qBittorrent official forums

I've tried changing some settings, but there are no noticeable changes at the moment.

Only few torrents are active at any given time, but mostly none of them are.
Upload speed hasn't been higher than 1 megabyte per second.

Tracker status on the loaded tasks.
Seed/Peer counts?
DHT node count

As has already been said already,  our suggested "settings" are a starting point, YOU now start testing to find the ideal for YOUR system and how you are running your client. There is no "one size fits all"

And why is 1 MiB/s 'slow'.

I consider 1MiB/s slow, because I know that my internet is much faster than that.

I would like to thank you for all your time, but it seems that qbittorrent in too advanced for me. I think I will just use an older version of utorrent, it works for me "straight out of the box" and I get much better upload download speeds with it.

I'm really thankful that you tried to help me though.

Best of Luck to you all!

I consider 1MiB/s slow, because I know that my internet is much faster than that.

Your Internet connection does not count, It is how quickly peers are willing to take pieces that count towards your upload rate.

ALSO your Internet connection is rated in bps === Bits per second whereas qBT rates are in Bytes per second.

I understand everything you are saying. And I understand that there are some differences between speed calculations in qbittorrent and utorrent.

But in the end everything comes down to megabytes and gigabytes.

You probably think I'm a bit crazy, but to prove my problem I just did a software comparison.

Qbittorrent
1. Used it for 1 month
2. Had 50+ torrents in it towards the end of the month
3. Only few gigabytes of data a day were ever uploaded
4. Didn't see higher upload speed than 1mb/s, but mosty they were below 100 kB/s
5. Torrents were mostly inactive
6. Tried various settings

uTorrent
1. Used it for one week
2. Have around 5 torrents now
3. Some days uploaded data can exceed 20 gigabytes. I have already uploaded 87.5 gigabytes of data just this week alone.
4. I constantly see upload speeds go above 1mb/s, even 6+ mb/s
5. Torrents are noticeably more active
6. Haven't even been messing with settings.

And were these exactly the same jobs that you tried in both clients?

Most of them were, yes.

[quote="wonderland"]
Most of them were, yes.
[/quote]

You only have 5 torrents in your uTorrent client. Even one torrent difference can make a huge difference. About 80% of my uploads are from 20% of my torrents.

If you're strictly seeding you should try making your cache as big as possible (aka 1800MiB) in the advanced settings.
This could increase your speeds too.

[quote="sledgehammer_999"]
If you're strictly seeding you should try making your cache as big as possible (aka 1800MiB) in the advanced settings.
This could increase your speeds too.
[/quote]

"as big as possible" what's the max? and would it affect download speed?

"as big as possible" is the number referenced in the post you are replying to!

and would it affect download speed?

The cache is for holding the active pieces (not the entire payload) of each running task.

it may not affect download speeds dramatically but as the post you are replying to states specifically "If you're strictly seeding" and this thread is about upload rates, having the "active pieces" cached means no "round trip" is needed to read the piece data from the hard drive before uploading.

ciaobaby wrote: "as big as possible" is the number referenced in the post you are replying to!

and would it affect download speed?

The cache is for holding the active pieces (not the entire payload) of each running task.

it may not affect download speeds dramatically but as the post you are replying to states specifically "If you're strictly seeding" and this thread is about upload rates, having the "active pieces" cached means no "round trip" is needed to read the piece data from the hard drive before uploading.

Thanks so much for your help (not a sarcastic answer, believe me), but I got some IO error about the torrent im seeding not having enough space (I set my caching to 1500MiB), didnt read the full error bc i panicked. Well, that an qBit crashed.

[quote="sledgehammer_999"]If you're strictly seeding you should try making your cache as big as possible (aka 1800MiB) in the advanced settings.
This could increase your speeds too.[/quote][quote="arzine"]Thanks so much for your help (not a sarcastic answer, believe me), but I got some IO error about the torrent im seeding not having enough space (I set my caching to 1500MiB), didnt read the full error bc i panicked. Well, that an qBit crashed.[/quote]The IO crash that occurs when the cache is set larger than ~1400 MB (or less if you have lots of torrents) ...still occurs last I looked:
http://qbforums.shiki.hu/index.php/topic,2042.0.html

I don't know if it happens when using the x64 version of qBT.

So set the cache to maybe 1000-1200 MB instead.
Also helps to raise cache duration to 600 seconds...otherwise it will just toss stuff out of ram rendering the cache almost worthless anyway. That duration should be longer for seeding!
If you're storing torrents on a spinning hard drive, DEFRAG it maybe once a week/month or after 50+ GB of downloading. qBT will be able to seed torrents off it faster as a result.
It doesn't help to defrag a SSD.

qBT with default settings results in extremely fragmented downloaded torrents:
http://pastebin.com/5M1TkXDr
...due to NOT using preallocate files.
While preallocate files helps immensely, that doesn't "save" SSDs because each write-in-place is almost certainly misaligned triggering absolutely immense write amplification.
I don't recommend downloading torrents using qBT to a SSD.

Deluge (which also uses libtorrent) has the same problem:
http://forum.deluge-torrent.org/viewtop ... 12&t=36959

uTorrent and no doubt other BitTorrent clients write whole pieces to disk in 1 sequential pass, which causes far less fragmentation than qBT and Deluge.

With a fast ISP, you could download smaller torrents to a ramdrive then have qBT automatically move them to either a SSD or HDD when done...which should vastly reduce fragmentation. But with a HDD, it's simpler and probably just as good to use preallocate files in qBT.
The move from ramdrive to HDD may cause qBT to slow down or stop downloading (and maybe uploading also!) due to being thread-locked until the move completes.[quote="wonderland"]I intend to maximize my upload speed which is very low at the moment, as regarding these setting, I have them like this:
Global maximum connection - 500
Maximum number of connections per torrent - 100
Global maximum number of upload slots - 8
Maximum number of upload slots per torrent - 4

Bottom line is that I would like to improve my upload speed in qbittorrent.[/quote]You almost certainly won't maximize your upload speed with those settings. You're only letting qBT upload to 8 peers/people spread between all your torrents at once -- if they can only download at ~1 MB/sec each that would average out to be ~8 MB/sec total. While many peers may download faster than that, they are likely downloading and uploading with others as well. Real-world upload speeds with just 8 upload slots is likely to average much lower than 8 MB/sec.

Because you seem to be in/near Singapore, I suggest setting upload slots even higher than might be the case otherwise. The undersea cables that Singapore uses to reach the "rest" of the internet are horrible bottlenecks. Either the cables themselves or upstream throttling of BitTorrent by ISPs to prevent those cables being overloaded causes most uploading/downloading to "distant" peers/seeds to be much-reduced.

So I suggest these settings instead:
Global maximum connection - 400
Maximum number of connections per torrent - 100
Global maximum number of upload slots - 300
Maximum number of upload slots per torrent - 80

I wouldn't recommend upload slots (global and per torrent) this high for *ANYONE* else, because most don't have 300+ mbit/sec upload bandwidth AND limited to <1 mbit/sec PER overseas peer.

Also due to the possible ISP throrttling/crippling of BitTorrent, I'd recommend either disabling DHT (but keep PEX!) or at least having DHT use a different port.
Try both Prefer and Require Encryption for a few hours or days each to see which one works best.

Global and per torrent max connections may "work around" the throttling better if set to 100 or less, but this is best tried only as a last resort.
Keep in mind that you may get better results at 1-6 AM your time because there's less traffic on/through your ISP and the undersea cables and your ISP may throttle less then.

arzine wrote:

ciaobaby wrote: "as big as possible" is the number referenced in the post you are replying to!

and would it affect download speed?

The cache is for holding the active pieces (not the entire payload) of each running task.

it may not affect download speeds dramatically but as the post you are replying to states specifically "If you're strictly seeding" and this thread is about upload rates, having the "active pieces" cached means no "round trip" is needed to read the piece data from the hard drive before uploading.

Thanks so much for your help (not a sarcastic answer, believe me), but I got some IO error about the torrent im seeding not having enough space (I set my caching to 1500MiB), didnt read the full error bc i panicked. Well, that an qBit crashed.

Then try setting the cache to 1000MiB and disabling os cache (also in advanced settings).
qbt is a 32bit process. 32bit processes can only address 2GB of RAM. So start low (1000MiB) and the start increasing until you experience problems. Max allowed in qbt is 1800MiB.
If you are also downloading, big cache would help only if you have an internet connection that is faster than what your disk's writing speed.
PS: The cache is unified and is shared. There is no distinct read/write cache. -I mean there is no separate limit for the 2-