[libtorrent] Delay with download progress in libtorrent 1.07

[Serhii Pavlenko]

Hi!
After migration from libtorrent v.:0.16.19 to v.:1.0.7 (or any 1.0.X),
there is a delay about 10 seconds until torrent_status.progress will be
non-zero, in case of any download rate limit (furthermore
rate_limit_ip_overhead=disabled).
Without session download rate limit - time delay is less than one second
(even with limitations with Netlimiter). v.0.16.19 in any case has a small
delay ~1 sec.
Are there some reasons for such behaviour in newest versions?
Thank you in advance.

Ragrds, Serhii

[Arvid Norberg]

Post by Serhii Pavlenko
Hi!
After migration from libtorrent v.:0.16.19 to v.:1.0.7 (or any 1.0.X),
there is a delay about 10 seconds until torrent_status.progress will be
non-zero, in case of any download rate limit (furthermore
rate_limit_ip_overhead=disabled).
Without session download rate limit - time delay is less than one second
(even with limitations with Netlimiter). v.0.16.19 in any case has a small
delay ~1 sec.
Are there some reasons for such behaviour in newest versions?

is it possible that you don't pass in the query_accurate_download_counters
to the status() call? That would only give you download progress when a
whole piece has completed.

see http://libtorrent.org/reference-Core.html#status_flags_t

[Serhii Pavlenko]

On Thu, Jan 14, 2016 at 4:10 AM, Serhii Pavlenko <sir.wolond <at>

gmail.com>

Post by Serhii Pavlenko
Hi!
After migration from libtorrent v.:0.16.19 to v.:1.0.7 (or any 1.0.X),
there is a delay about 10 seconds until torrent_status.progress will be
non-zero, in case of any download rate limit (furthermore
rate_limit_ip_overhead=disabled).
Without session download rate limit - time delay is less than one second
(even with limitations with Netlimiter). v.0.16.19 in any case has a small
delay ~1 sec.
Are there some reasons for such behaviour in newest versions?

is it possible that you don't pass in the

query_accurate_download_counters

to the status() call? That would only give you download progress when a
whole piece has completed.
see http://libtorrent.org/reference-Core.html#status_flags_t

Hi!
Thanks for help, the problem was caused by
query_accurate_download_counters.

Regards, Serhii

[Serhii Pavlenko]

On Thu, Jan 14, 2016 at 4:10 AM, Serhii Pavlenko <sir.wolond <at>

gmail.com>

Post by Serhii Pavlenko
Hi!
After migration from libtorrent v.:0.16.19 to v.:1.0.7 (or any 1.0.X),
there is a delay about 10 seconds until torrent_status.progress will be
non-zero, in case of any download rate limit (furthermore
rate_limit_ip_overhead=disabled).
Without session download rate limit - time delay is less than one second
(even with limitations with Netlimiter). v.0.16.19 in any case has a small
delay ~1 sec.
Are there some reasons for such behaviour in newest versions?

is it possible that you don't pass in the

query_accurate_download_counters

to the status() call? That would only give you download progress when a
whole piece has completed.
see http://libtorrent.org/reference-Core.html#status_flags_t

Hi!

Sorry for inconvenience, there was a mistake from my side: the problem
still can be reproduced(it's not connected with query_accurate_download)

Some additional information: size of test file ~2GB, piece size - 2MB,
lsd, dht are enabled, also there are a weeb seeds avilable for this
torrent.

Thank you in advance, Serhii

[Arvid Norberg]

does client_test (under examples) reproduce this?
if so, would it be possible for you to send me a test torrent that I can
reproduce it with?

Post by Serhii Pavlenko

On Thu, Jan 14, 2016 at 4:10 AM, Serhii Pavlenko <sir.wolond <at>

gmail.com>

Post by Serhii Pavlenko
Hi!
After migration from libtorrent v.:0.16.19 to v.:1.0.7 (or any

1.0.X),

Post by Serhii Pavlenko
there is a delay about 10 seconds until torrent_status.progress will

be

Post by Serhii Pavlenko
non-zero, in case of any download rate limit (furthermore
rate_limit_ip_overhead=disabled).
Without session download rate limit - time delay is less than one

second

Post by Serhii Pavlenko
(even with limitations with Netlimiter). v.0.16.19 in any case has a

small

Post by Serhii Pavlenko
delay ~1 sec.
Are there some reasons for such behaviour in newest versions?

is it possible that you don't pass in the

query_accurate_download_counters

to the status() call? That would only give you download progress when

a

whole piece has completed.
see http://libtorrent.org/reference-Core.html#status_flags_t

Hi!
Sorry for inconvenience, there was a mistake from my side: the problem
still can be reproduced(it's not connected with query_accurate_download)
Some additional information: size of test file ~2GB, piece size - 2MB,
lsd, dht are enabled, also there are a weeb seeds avilable for this
torrent.
Thank you in advance, Serhii
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Libtorrent-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss

[Serhii Pavlenko]

Post by Arvid Norberg
does client_test (under examples) reproduce this?
if so, would it be possible for you to send me a test torrent that I can
reproduce it with?

Hi!

This problem can be reproduced on client_test as well, with the
following parameters:
test.exe -k -z -N -h -H -M -d 1000 "Archlinux 2016.02.01 dual.torrent"
on the following torrent: http://bit.ly/1PbbyKb.

On v. 0.16.19 time when we have total_done > 0 in my case about 11
seconds, while on v. 1.0.8 - about 5 seconds.

Regards, Serhii.