Total byte control !

[nico910]

Hello, sorry for my bad english, i don't write this request for fun, i write it cause i've serious problems with qBittorent with use of optic fiber, i can't seed at my maximum capacity

Problems:
- HDD 100% busy when i dowload, then Windows laggy if i use a busy hdd
- no equality between trackers for upload.
- too many software limits for download and upload. Solved: with qb 3.2.0
- crashs when i don't set upload limits  Identified:memory cache limit is not efficient, if i set  1000MB limit qbt use 1400MB, no crash with qb 64 bits but same problem W.i.P for 32 bits

Main reason: optic fiber is faster than any HDD, we have to prepare the futur.

Solutions and idea:
- Let the users type the desired download or upload limits without any restriction ! who cares about the slider ? Solved with qb 3.2.0
- Ability to limit a category for: 

• limit a HDD to 15MB/s for example, to prevent 100% use.
• limit trackers to 5MB/s for example for better seeding equality.

- Add sub tag to set for example:
  Parent category->"HDD 1" limited to 15MB/s

• Child tag-> "Tracker 1" limited to 6 MB/s
• Child tag-> "Tracker 2" limited to 6 MB/s
• Child tag-> "Tracker 3" limited to 6 MB/s
• Child tag-> "Tracker 4" limited to 6 MB/s

the difficulty is other HDD can use the same trackers
  Parent category->"HDD 2" limited to 15MB/s

• Child tag-> "Tracker 1" limited to 6 MB/s
• Child tag-> "Tracker 2" limited to 6 MB/s
• Child tag-> "Tracker 3" limited to 6 MB/s

so the tag has a global effect but a category has a local effect.
- Abilitty to use 8MB and 16MB pieces size for torrent creation, then as said sledgehammer999, add a dialog where the user can input any value (multiple of 16KB though)

my qBittorent config:
- no conexion limits
- 500 Torrents (lot of big torrents like 100GB packs, stored on HDD only)
- several trackers (public or private)
- 1 category per HDD, 1 category per tracker.
- upload limit set to 10MB/s can't more and if i don't set limit by bandwidth is 100% busy or qB crash Solved with qb 3.2.0
- my total seed since one year : >60TB

my PC config:
- 5 HDD (18 TB)
- 1Gbit/s down, 200Mbit/s up(theorical)
- 12GB DDR5
- Windows 8.1 on ssd
- CPU i7-5930k @3.5Ghz

[ciaobaby]

i can't seed at my maximum capacity

And you probably NEVER will, unless your client is the ONLY seed for a torrent that many hundreds of people want to download.

500 Torrents (lot of big torrents like 100GB packs, stored on HDD only)

You are running the wrong client, AND the wrong operating system. You need one that has NO additional load of a GUI, and an operating system that doesn't have the caching problems of Windows.

I would suggest that you should be running rTorrent on SlackWare Linux or on Centos.

[nico910]

And you probably NEVER will, unless your client is the ONLY seed for a torrent that many hundreds of people want to download.

no man, you don't realize i'm seeding more than 10 TB of files... see i just took a screenshot right now, i removed the upload limit.
Also when im uploading i'm always at  22MB/s, i upload a lot of video packs



edit: but now qb crashed

You are running the wrong client, AND the wrong operating system. You need one that has NO additional load of a GUI, and an operating system that doesn't have the caching problems of Windows.

I would suggest that you should be running rTorrent on SlackWare Linux or on Centos.

Ok. i can understand but i can't change my pc, all my familly use it me and my brother play a lot of video games working on windows only

edit: i tried to uncheck "Enable OS cache" like said here https://github.com/qbittorrent/qBittorr ... /1131  i 'll try some hours to see

edit 2 : unfortunately qB is still crashing

[ciaobaby]

no man, you don't realize i'm seeding more than 10 TB of files... see i just took a screenshot right now,

Who cares? It is of absolutely no consequence whether you are 'seeding' 10MB or 100TB, if there are other seeds to connect to, your client is NEVER going to get as many downloading peers or the volume of data-transfer as you think you deserve, it simply is not going to happen and you should not expect it to happen. What you get IS what you get and there is ABSOLUTELY NOTHING that you can do to make peers take more that they want to take from your client. You are NOT in control of how fast downloads will actually go, ... ... YOU can only control the potential or the maximum that download speeds can possibly reach.

[nico910]

Who cares? It is of absolutely no consequence whether you are 'seeding' 10MB or 100TB, if there are other seeds to connect to

Yes but there is no other seeds to connect when i'm the uploader and/or the only seeder of a 200 GB torrent. + all other seeders doesn't have optic fiber. and as you should know, upload capacity for most peoples = dowload capacity/8
Also when i upload a new 200 GB torrent ( i actually split it in 4 torrents since actual max qB packet size is not enought for some trackers who limit number of packet) i actually limit it to 8MB/s so 2MB/s are remaining for other Torrents since the max global upload limit is 10MB/s
I would limit this new torrent to 18MB/s for example and global to 20MB/s. cause while i'm the only seeder of this last torrent, all my 500 other torrents are limited to 2MB/s
This is a big problem for leechers.
Sorry if my explanation is bad, i've some difficulty with english, but trust me actual qB limits are a big problem for me and leechers

[sledgehammer_999]

The limit box can have any value inputted now in v3.2.0 (see alpha builds in Windows Development subforum).
The seeding/downloading may be limited by your CPU too. See here why: https://code.google.com/p/libtorrent/is ... ail?id=552
And about the piece size: open a request in the bug tracker.

PS: Do the crashes display any message at all? When it is about to happen what is the qbt RAM usage and what is the system total usage?

[nico910]

Hello, thanks sledgehammer_999, i'll try alpha
Crashes does not display any message, current active torrents are paused then qb just disapear, i've 12Gb ram and the total usage of ram is never above 7GB, i didn't watched how qB use ram i 'll retest now....
i removed limits and qB is using 1800 MB,  i'll wait some time to see.. i noticed its 32 bits, does that mean qB can't use more than 4GB ?
edit: qb just crashed at 1800MB i think, now i'll try alpha....

edit 2 :my cpu is i7-5930k @3.5Ghz

edit 3: no longer crash with this alpha http://qbforums.shiki.hu/index.php/topi ... l#msg15099 i'll stress qb for 1 hour to see..

edit 4: for the HDD 100% busy i found an explenation on google

The physical head movement (latency) is what will slow a transfer from a spinning platter disk. If you were copying from a single HDD, then you would start a single big transfer rather than lots of small ones. The head going back and forth between two or more files that are being copied is what slows the transfer. Of course you would get the same effect if the HDD were heavily fragmented even if you were copying a single file.

after months of use i can say, if i dowload a torrent with a single file my hdd can write 70MB/s but if i dowload several torrents with several files like video packs , my HDD is 100% busy at 10MB/s  (size of pieces change a lot of thing too, with small pieces the HDD is very slow), i can increase speed with sequential download but only if there is a lot of seeders.
That's why i request the ability to limit a category

edit 5: about the piece size, it's not really a bug, i created a 320GB torrent with 4MB pieces, that work, but when i try to upload on some tracker, the tracker does not accept probably cause there is too many pieces. 8MB or 16MB pieces solve the problem but i had to use an other software that not cool

edit 6: after some hours qb alpha 3.2.0 crashed the problem seems come from big torrents at hight speed, i'm not sure but i realized crash occur since i've downloaded 2 video packs 60 GB torrents with 16MB pieces, but i've a lot of small files(<10GB) with 8MB and 16MB piece who don't cause problems, i'll try to pause the 2 packs and retest....well i'll go to sleep and feed back later

edit 7:qb crashed again this night now i paused 21 torrents for testing , all my torrents who have 8MB or 16 MB pieces.

edit 8: no longer crash since i paused all my 21 torrents whith 8MB and 16MB pieces, also, for the same upload speed (16MB/s) qb is using only 1500MB ram instead of 1800MB so i guess several torrents with big pieces is the cause of crashs.

edit 9 : after some hours qb work perfectly and use 1700MB ram max near of my maximum upload speed.


so i'm pretty sure the problem is from the fact to have several big torrents actives using 8MB or 16MB pieces, i hope you'll find how to solve the problem

[ciaobaby]

i noticed its 32 bits, does that mean qB can't use more than 4GB ?

2GiB is the maximum memory ANY 32bit application can address and the closer you set the cache to 1800 MB the closer you get to a application crash.

[nico910]

Thanks ciaobaby so that's why my qb crashed i guess.
Well i will try the 64 bits build to be sure...
I'm testing https://www.dropbox.com/sh/h5n5pl997ebi ... p.exe?dl=0 unfortunately the upload limit max is 10MB but i'll test some hours without limits to verify if it crash...

[sledgehammer_999]

Try again my alpha but set a cache limit to 1400MiB and disable OS cache, while also using 8MB and 16MB piece size torrents. Will it still crash?

EDIT: Yes piece size in torrent creator isn't a bug. The bug tracker is used for feature requests too though.

[nico910]

Is it disk write cache size ?
I tried yesterday to set limit to 1500MiB and i disabled os cache then qb crashed.
I'm sorry but i'll no longer use 32 bits if i'm limited by the software, i can accept to be limited by the hardware but nothing else, i'm using only 1080p(most x265) videos for now, imagine the problems with 4k and 8k videos ?

edit: i posted a request for pieces size but i don't understand how github work, first time i use it so i'am not sure i posted at the right place sorry :/
i can't delete or modify my request ? cause i didn't selected the good commits i think :/

edit2: then can i post a request for "ability to limit the speed for a catégory" ? because it's the most important feature i need to control all my HDD to prevent 100% usage. very important !

[ciaobaby]

Is it disk write cache size ?

Let's get the fallacy out of the way first.

You do NOT need a huge cache setting. The cache size only needs to be a large as the number of 16k blocks that are active at any one time (up or down), plus a small amount of overhead, and by small we are talking in kilobytes. Setting a GiB size cache will not really help with speeds in either direction and may actually worsen the performance rather than improve it.

Let the client manage the cache, it can do a far better job than you can, and it can do it much, much quicker, but if you are going to micro-manage, do it by keeping the cache BELOW the 5 - 10 Mib level will make more sense from a client stability viewpoint.

250 MiB upwards only starves other applications of memory, while making BitTorrent client behave and perform badly.

[sledgehammer_999]

About the issue request: I gave you instructions on how to open it properly.
About the crashing: Are you willing to help debug this? Normally qbt shouldn't crash even though it is 32bit. However, I don't have so high loads and cannot reproduce the crash. If you want to help with this, I'll post instructions on what to do.

[nico910]

Hello thanks for your help guys
I used the qb 64 bits version with 8MB and 16MB pieces torrents actives all the night without crash. and seeded 485 GiB
the two 60GB torrents with 16MB pieces were the most active as you can see:



sledgehammer_999 of course i will help you to identify the problem but i'm totally noob i need very newbie instructions. you said set the cache to 1400 MB but i don't know where to type this number :/
thanks guys.

[Nemo]

you said set the cache to 1400 MB but i don't know where to type this number :/

Its probably the ''disk write cache size'' within the ''advanced'' settings.