Re: Download and upload rate limits problem

On Aug 31, 2007, at 00:05, Olivier Mouchet wrote:

> Hi,
>
> I used the simple_client example to test the upload and download rate
> limits, and it seems that the limits are correctly set up (with a  
> session.
> download_rate_limit() I can check that the limit has been
> taken in account) but the actual bandwith become higher than the  
> limit.

Is it significantly higher?

There is one special case where the rate limit is violated, all new  
connections get 100 bytes "free", just to make sure they can transfer  
the handshake.

--
Arvid Norberg

> In the simple_client exemple, I just add a limitation at 1.5KB just  
> after
> the session constructor
> s.set_download_limit_rate(1500) ;
>
> Once a torrent has been added to the session, I print regularly the  
> real
> download rate:
> session_status status;

Re: torrents priority

I would really like this feature too. Arvid, the last method you gave seem good enough, better than pausing
torrents with lower priorities anyway :)

Regards,
Chris.

----------------------------------------> From: arvid <at> cs.umu.se> Date: Tue, 28 Aug 2007 09:23:53
-0700> To: libtorrent-discuss <at> lists.sourceforge.net> Subject: Re: [libtorrent] torrents
priority>> On Aug 27, 2007, at 04:42, Olivier Mouchet wrote:>>> Hi again,>>>> Tell me if I'm wrong, but I
guess there's no method to prioritize a>> particular torrent in a session.>> Correct. Except pausing
torrents that are not prioritized.>>> In consequence, I thought to emulate it in manipulating torrents'
rate>> limits:>> _ if the sum of each torrent's rate is under the session's rate>> limit, don't>> do
anything>> _ else decreasing lower-priority torrents' rate limit regarding the>> difference between
the sum of each torrent's rate and the session's>> rate>> limit.>>>> This is a first idea, far to be
perfect. But if we do not focus on the>> algorithm, I wonder if it will be efficient (and does not represent
an>> instability factor) to modify the torrents' rate limits in a very>> frequent>> way?>>>> Did anyone
have a reflexion about ways to give priorities to>> torrents using>> libtorrent? Or have an idea about the
algorithm implemented in some>> other>> clients? Do they manipulate rate limits too?>> It depends on
what you mean by "priority".>> The most reasonable semantics I can think of for priority on torrents> is to
stop all non-prioritized torrents until the prioritized ones> have finished downloading. Possibly
with some way of starting more> torrents in case the bandwidth is not saturated.>> It would also be
possible to have all the peers from a prioritized> torrent skip ahead all peers from lower priority
torrents when they> get in line to request upload bandwidth quota from the rate limiter.> That would
basically mean that the upload bandwidth is given to high> priority peers, and the left-overs are used for
other peers.>> --> Arvid Norberg>>>>
-------------------------------------------------------------------------> This SF.net email
is sponsored by: Splunk Inc.> Still grepping through log files to find problems? Stop.> Now Search log
events and configuration files using AJAX and a browser.> Download your FREE copy of Splunk now>>
http://get.splunk.com/> _______________________________________________> Libtorrent-discuss

Assert Fail

I just compiled the libtorrent and simple cilent with VC7.1 on windows XP.
When I try to use the simple client with a torrent file, an assertion
exception thrown out,
the assert is fialed on peer_connection.cpp#line 2156

        if (!m_in_constructor && t->connection_for(remote()) != this)
        {
            assert(false);
        }

but if I remove these statements, another assert will fail, that assert is
on invariant_check.hpp#line 43

Why they fail and how can I solve them?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Assert Fail

On Sep 1, 2007, at 04:58, skywoody wrote:

> I just compiled the libtorrent and simple cilent with VC7.1 on  
> windows XP.
> When I try to use the simple client with a torrent file, an assertion
> exception thrown out,
> the assert is fialed on peer_connection.cpp#line 2156
>
>         if (!m_in_constructor && t->connection_for(remote()) != this)
>         {
>             assert(false);
>         }
>
> but if I remove these statements, another assert will fail, that  
> assert is
> on invariant_check.hpp#line 43
>
> Why they fail and how can I solve them?

Please file a ticket at http://code.rasterbar.com/libtorrent/ 
newticket with the stack strace to the assert (i.e. run it in a  
debugger). File it against 0.12.

thanks,
--
Arvid Norberg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.

Re: question about comments

On Sep 2, 2007, at 02:13, skylian1985 wrote:

> I am confused by the comments in peer_connection.hpp.I wander what  
> "this peer" refers to. Is it the local peer or the remote peer?thanks.

I typically use "client" to refer to the local libtorrent client, and  
peer to refer to a remote client we may be connected to.

--
Arvid Norberg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Libtorrent-discuss Digest, Vol 16, Issue 3

Does that means the member m_ses of peer_connection is the session of the remote client, for the comment of
it is "a back reference to the session the peer belongs to"? Another question is:I wanna do some statistics
on a peer community. Given a torrent, how can one peer get to konw all the other peers associated with that
torrent?  
在2007-09-04，libtorrent-discuss-request <at> lists.sourceforge.net 写道：
Send Libtorrent-discuss mailing list submissions to libtorrent-discuss <at> lists.sourceforge.net To
subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss or, via email, send a message
with subject or body 'help' to libtorrent-discuss-request <at> lists.sourceforge.net You can reach the
person managing the list at libtorrent-discuss-owner <at> lists.sourceforge.net When replying, please
edit your Subject line so it is more specific than "Re: Contents of Libtorrent-discuss digest..."
Today's Topics: 1. Re: question about comments (Arvid Norberg)
---------------------------------------------------------------------- Message: 1 Date: Mon, 3
Sep 2007 11:28:26 -0700 From: Arvid Norberg <arvid <at> cs.umu.se> Subject: Re: [libtorrent] question
about comments To: General discussion about libtorrent
<libtorrent-discuss <at> lists.sourceforge.net> Message-ID:
<2FFC220D-DCD3-43C3-A178-B1D75F1E0377 <at> cs.umu.se> Content-Type: text/plain; charset=US-ASCII;
delsp=yes; format=flowed On Sep 2, 2007, at 02:13, skylian1985 wrote: > I am confused by the comments in
peer_connection.hpp.I wander what > "this peer" refers to. Is it the local peer or the remote
peer?thanks. I typically use "client" to refer to the local libtorrent client, and peer to refer to a
remote client we may be connected to. -- Arvid Norberg ------------------------------
------------------------------------------------------------------------- This SF.net email
is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log
events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >>
http://get.splunk.com/ ------------------------------
_______________________________________________ Libtorrent-discuss mailing list
Libtorrent-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss End of Libtorrent-discuss
Digest, Vol 16, Issue 3 *************************************************

Noob question: trackerless torrents

Hi,

I'm trying to setup a torrent network on my LAN. I created the torrent using
make_torrent. And started client_test on both machines on the network. But,
the peers never seem to find each other. No firewall problem, I checked. Is
it the case of trackerless torrents?

Any help will be appreciated.

Thanks,
Amol.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Noob question: trackerless torrents

On 9/6/07, Amol <babaiscool <at> gmail.com> wrote:
> Hi,
>
> I'm trying to setup a torrent network on my LAN. I created the torrent using
> make_torrent. And started client_test on both machines on the network. But,
> the peers never seem to find each other. No firewall problem, I checked. Is
> it the case of trackerless torrents?

uTorrent just got support for "local peer discovery" which is exactly
what you need.  I'm not certain if libtorrent supports this yet.

--

-- 
Cory Nelson
http://www.int64.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: ip address problem of peer_connection

Quoting skylian1985 <skylian1985 <at> 163.com>:

> I use peer_connection's m_socket to get the local and remote ip/port of a
> connection, but sometimes i got ip 0.0.0.0 from m_socket.local_endpoint(),

That's probably before the socket has been connected.

> why and how can i get the correct ip from peer_connection?

The remote endpoint is stored in m_remote. This is set when the peer_connection
is constructed, and will be valid regardless of the socket's state.

The local IP and port can probably only be obtained after the socket has been
connected. Which is done in peer_connection::connect()

--

-- 
Arvid Norberg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: ip address problem of peer_connection

>The remote endpoint is stored in m_remote. This is set when the peer_connection
>is constructed, and will be valid regardless of the socket's state.
>The local IP and port can probably only be obtained after the socket has been
>connected. Which is done in peer_connection::connect()
I got the local ip address when peer_connectio calls disconnect(), but found the ip is "0.0.0.0", is that
because libtorrent made local ip address to be "0.0.0.0" before calling disconnect()?
--
Arvid Norberg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Libtorrent-discuss mailing list
Libtorrent-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss