Got a question about speed in general

[SplitNarcissist]

I was just wondering if say around 60 kB/s download is good for a 10mb connection? I read the speed tweaking guide but don't want to mess with all that stuff if my speed is good as is.

Thanks

[Ultima]

It really depends on your torrent. Try a faster one, like OpenOffice.org 2.0.2, just to check if everything's okay.

[Firon]

Ctrl G, pick your upload speed, make sure you get a green light, turn on protocol encryption.

[SplitNarcissist]

Ctrl G, pick your upload speed, make sure you get a green light, turn on protocol encryption.

It now seems to be staying around 75 kB/s.

Just want to ask, if my upload speed on average is around 730-740, should I pick 768 or 640 for my upload speed?

[DreadWingKnight]

Round down, not up or to the nearest.

[Firon]

I would say 768, since "768" would be the value not counting any overhead. You may wanna play with the upload cap to see what gives you best results.

So, you turned on Protocol Encryption too and restarted the torrents afterwards?

[jult]

You may also want to try my reg-patch. It's quite popular here in The Netherlands (about 50 downloads a day for the .reg file) and it's entirely safe (its content is shown).

You can get it here: http://jthz.com/speed/ (the link saying 'Download Registry Patch' is the one you want)

just download and Open it, confirm Entering it in your registry, and after the next reboot it's active.

The page is in Dutch, but basically all you need to know is:

- Make a backup of your registry (Windows XP has this built in with the creation of rollback/return points), or you can use a tool called ERUNT for making a full registry backup and restore option available.

- It also contains a color-scheme, and in some cases that'll be active after reboot. Just switch to your old theme if needed.

- Among many well-tested changes it sets the TCP Receive Window (RWIN) size to 256960, which is working just fine for bittorrent.

It's a collection of reg-patches which I created for personal ease of use at work and at home. It contains security and speed-related changes to the registry that have been thoroughly tested. It will not mess things up, and in the extremely rare case that it might you will have your backup, but I have yet to recieve a complaint from it. ;-)

[splintax]

Hrm, I dunno, changing the size of the RWIN isn't for everyone. Probably better suited to a tool like DrTCP..

[jult]

It applies to everyone using broadband with speeds higher than 512 kbps, unless you're using a 486 with 24 MB of RAM.

DrTCP does exactly that: Change the RWIN

you can't trust software like that any more than my patch.

Try http://www.speedguide.net/analyzer.php for a check on your RWIN.

[Firon]

setting too high RWIN values can make it worse, better to actually customize it on a per-connection basis

[SplitNarcissist]

I just peaked out at 105 kB/s for a slight bit, but it's mostly staying around anywhere from 70-90 kB/s. Though for the record, my actual download speed that I get is 7mb-8mb with TCP overhead counted. I don't get my full 10mb speed.

So is 70-90 kB/s good for say 7mb connection? Plus, is it normal for the speed to take a bit to get a regular speed going? Like it takes anywhere from 5-12% done for it to be at a steady speed. It starts out slow though, going from 1 to the 70's.

So maybe I should try some of the suggestions in the speed guide. Mostly the updating stuff, cause the rest seems to be out of my league.

EDIT: At 150-160 kB/s right now with with 50% done of the file. Nothing was changed either, still have it with PE enabled and the upload speed at 768.

[Kazuaki Shimazaki]

Realistically, you should be quite pleased with even 60. The reality of the situation is that your DL is usually limited by your upload in a decreasing utility curve in which extra upload does not buy you very much in terms of download.

Occasionally, a guy with a fat upload pipe will come along and you can saturate your own DL pipe, but it doesn't happen very often. Honestly, if you can get 150-160 at the halfway point (generally, half is very roughly when you are most likely to get your best speeds), you should be ecstatic.

As for rampup - yes, it happens. You can patch your TCPIP.sys to have more half-open connections and it'd help a bit, but basically don't plan on getting anywhere close to your best as much as an hour and the best speeds will most likely come somewhere between the 40-80% points. After 80% fewer guys will have what you need and you're more likely to slow again, while below 40% you don't have enough of what others need. Still, really, for the really good speeds it is luck - get fat guy to stuff your pipe by accident.

These are my experiences anyway.

[Metatron]

If the torrent is just posted, much of the speed depends on that of the actual first seeder.

And Firon, yes, recievwindow shouldn't be too high, but the one jult picked is low enough to allow caching to not delay responses. jult: I was surprised to find some speed hacks I didn't know yet in your reg file. Also thanks for the NoLanMan password hash entry, I was not aware of that!

[splintax]

setting too high RWIN values can make it worse, better to actually customize it on a per-connection basis

Precisely, that's why you should use a tool like DrTCP or manually patch the registry rather than just applying a "cure-all" patch.

And 150 KiB/s is pretty decent for a public torrent (hell, anything over 30 KiB/s is) but I wouldn't be "ecstatic" over it. However, on private torrents, people routinely see speeds over 1 MiB/s...

[SplitNarcissist]

I was also reading up on the faq more. The faq pretty much states that as long as you get around your upload speed, that you are going good.

Considering I get a bit higher than that now with RE enabled, I'm quite happy. Thanks for all the info and tips. Loving UTorrent btw, best torrent program I ever had.