Speed limiter related bugs

[Whirligig]

I have a few issues with the speed limiter

Firstly, it works brilliantly unless SSL is enabled. With SSL enabled, the speed bounces wildly around my desired speed before eventually settling on 0KBps, also I receive strange critical error messages such as:


[23:21:23] ERROR NNTPSocket - NS_Connect - news.usenetserver.com-Error talking to Server:244299306 (023/105) "nn934251022.part022.rar" - 4.61 GB - yEnc (4/79) JBinUp.com <JBinUp@JBinUp.local> Fri, 16 Mar 2012 01:19:15 GMT <7RFb52xhsnKqbEHutB1U_23o105@JBinUp.local> 663734 5101 Xref: news.usenetserver.com alt.binaries.boneless:244299306

[23:22:24] ERROR NNTPSocket - NS_Connect - news.usenetserver.com-Error talking to Server:244299308 Captain Jack O'Neill Posts Stargate SG-1: Season 8 (DVD9 Remux 2 MKV) - [12/33] - "StarGate.SG-1.S08E16.Reckoning.Part.1.576i.DVD.MPEG2.DD5.1.r10" (63/82) Capt.J.ONeill@CheyenneMountain.com.plex (Captain Jack O'Neill) Fri, 16 Mar 2012 02:19:15 +0100 <part63of82.LGQUk9IWyHjJ9Nk9ZB1J@camelsystem-powerpost.local> 661152 5080 Xref: news.usenetserver.com alt.binaries.boneless:244299308

[23:22:55] ERROR NNTPSocket - NS_Connect - news.usenetserver.com-Error talking to Server:244299309 [05/36] - "Marsupilami_cbr.part04.rar" yEnc (3/66) CPP-Gebruiker <CPP-gebruiker@domein.nl> 16 Mar 2012 01:20:28 GMT <FS17V5prGYMokPvbSoR@JBinUp.local> 398249 3059 Xref: news.usenetserver.com alt.binaries.boneless:244299309 alt.binaries.nl:355615244

[23:24:27] ERROR - SSL Read Failed: 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[23:24:27] ERROR NNTPSocket - Server:news.usenetserver.com NNTPServer: Timeout - Waiting for Server to send Data: Socket - Read or Write Timeout

I have no idea what these NS_Connect errors are and I'm not downloading or indeed recognise any of the files mentioned.

Note, none of these issues occur with SSL disabled.

The second issue is related to another possible bug. With XFeatures enabled and downloading headers Newsbin is reporting my downloaded speed as over 4.5MBps, when my actual download rate is closer to 0.6MBps, I guess this is because the headers are being compressed and send at ~600KBps but Newsbin isn't aware of the data until it's decompressed, at a ratio of ~8-9:1 and thus accidently inflating my download rate by 8.

Due to this, when enabling the speed limiter when downloading group headers, Newsbin attempts to restrict downloads to the desired speed, eg 200KBps, unfortunately as it's only counting the data downloaded AFTER it's been decompressed, this drops my actual newsbin download rate to roughly an 1/8th of 200KBps, the actual behaviour manifests itself as a 150KBps spike for 1 second followed by 8-9 seconds of nothing. Instead of the sustained throughput of 200KBps expected. This behaviour occurs regardless of SSL or not.

I'm using the windows 7 firewall, which has newsbin allowed, my only antivirus is the Microsoft Security Essentials and I have the firewall disabled on my router. Any ideas?

[Quade]

The second issue is related to another possible bug. With XFeatures enabled and downloading headers Newsbin is reporting my downloaded speed as over 4.5MBps, when my actual download rate is closer to 0.6MBps, I guess this is because the headers are being compressed and send at ~600KBps but Newsbin isn't aware of the data until it's decompressed, at a ratio of ~8-9:1 and thus accidently inflating my download rate by 8.

The BW limiter is based on the bytes read raw off the network, not on the decompressed size so, what you think is happening isn't. The reported speed is the decompressed data speed though as you guessed. It's no accident. It's reporting the decompressed data speed on purpose.

Basically it's

----Read Raw------|
----Read SSL------| Count the bytes/Slow down | ----- Decompress -----| Calc Speed/Process.

There's a possibility that you're setting speeds below where it works properly. It's something I'll have to check. SSL reads data off the network in a way that's invisible to Newsbin until SSL decides to hand the decrypted data to Newsbin. I hadn't really considered it but, that might cause some issues.

How many connections are you using? At the speed you're downloading you might want to only us 1 or 2 connections. That can smooth the data out too.

[Whirligig]

I've dropped my connections from 20 to 5. Speed limiter is now behaving itself and no more crazy errors about files I'm not even downloading, thanks!

Still seeing incorrect throttling for Xfeature headers though.

With files, if I set the limiter to 409.8KBps then NB shows ~460KBps and I'm seeing out of the process 420KBps +/- 50KBps as it wobbles around.

With headers, with limiter set to 409.8KBPS then NB shows ~460KBps but I'm only seeing occasional pulses of 60-80KBps.

It really looks as if the limiter is throttling according to the NB speed output and not the actual download speed. Happy coincidence perhaps.

EDIT: Tried downloading headers with SSL off. The limiter works fine. Must be an issue with SSL

[Nasty64]

I'm seeing the same issue. No limiting I see 55Mb constantly. Try to limit it to 42Mb and it fluctuates wildly, usually in the 20Mb range. Using SSL, and 8 server connections (though I've tried 6 and 15).