Unofficial 64-bit installer/archive 3.3.x
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="Switeck"]
People having issues running 32bit qbit on a 300+ mbit connection should be fixed.
A workaround till then could be to not allow qBT to use more than 1000 MB for cache even when cache is set to automatic.
Far as I know, that's the only show-stopper that the 32bit version has that the 64bit version doesn't...however the 64bit version can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version are you using that can use 5.5gb ?
Because 3.3.6 and 3.3.7 are always stuck at 663mb no matter which setting i chose, auto cache size and expiry at 600s or default 60s. Active download using 200/300 mbit down and 500/700mbit upload or idle doing al most nothing, stays at ~663mb.
People having issues running 32bit qbit on a 300+ mbit connection should be fixed.
A workaround till then could be to not allow qBT to use more than 1000 MB for cache even when cache is set to automatic.
Far as I know, that's the only show-stopper that the 32bit version has that the 64bit version doesn't...however the 64bit version can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version are you using that can use 5.5gb ?
Because 3.3.6 and 3.3.7 are always stuck at 663mb no matter which setting i chose, auto cache size and expiry at 600s or default 60s. Active download using 200/300 mbit down and 500/700mbit upload or idle doing al most nothing, stays at ~663mb.
Last edited by fusk on Fri Oct 07, 2016 5:59 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
You'd have to manually set the cache size much larger -- as high as 4096 MB for qBT 64bit version or 1536 MB for qBT 32bit version...to really see ram use climb.
Also you'd have to have the cache expire at 600 seconds (max allowed sadly) and have download and/or upload speeds far in excess of 10 MB/sec (~80-100 mbit/sec).
In my Extreme speed tests, I was seeing speeds of just over 100 MB/sec...but I initially triggered the cache overload crashes with only ~650 KB/sec upload speed on a single busy torrent. (it was >10 GB size tho.)
Also you'd have to have the cache expire at 600 seconds (max allowed sadly) and have download and/or upload speeds far in excess of 10 MB/sec (~80-100 mbit/sec).
In my Extreme speed tests, I was seeing speeds of just over 100 MB/sec...but I initially triggered the cache overload crashes with only ~650 KB/sec upload speed on a single busy torrent. (it was >10 GB size tho.)
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="Switeck"]
You'd have to manually set the cache size much larger -- as high as 4096 MB for qBT 64bit version or 1536 MB for qBT 32bit version...to really see ram use climb.
Also you'd have to have the cache expire at 600 seconds (max allowed sadly) and have download and/or upload speeds far in excess of 10 MB/sec (~80-100 mbit/sec).
In my Extreme speed tests, I was seeing speeds of just over 100 MB/sec...but I initially triggered the cache overload crashes with only ~650 KB/sec upload speed on a single busy torrent. (it was >10 GB size tho.)
[/quote]
Well, to be fair, i did mention using expiry at 600s and speeds up to 7 times higher than the 10mb/s you mention. Sadly my drives overload if i go above 40mb/s download if i'm uploading 700/800+ mbit at the same time, which btw is normal for me. But my max speed down and up is ~110mb/s, or ~170mb/s simultaneous before my wan port caps out.
But i have not used manual cache size, i've always left it at auto, and just increased the expiry. Also, i found out it was lib1.1 that caused being stuck at 663mb. Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s. But it didn't want to go above 1.9gb, not sure what's going on there.
You'd have to manually set the cache size much larger -- as high as 4096 MB for qBT 64bit version or 1536 MB for qBT 32bit version...to really see ram use climb.
Also you'd have to have the cache expire at 600 seconds (max allowed sadly) and have download and/or upload speeds far in excess of 10 MB/sec (~80-100 mbit/sec).
In my Extreme speed tests, I was seeing speeds of just over 100 MB/sec...but I initially triggered the cache overload crashes with only ~650 KB/sec upload speed on a single busy torrent. (it was >10 GB size tho.)
[/quote]
Well, to be fair, i did mention using expiry at 600s and speeds up to 7 times higher than the 10mb/s you mention. Sadly my drives overload if i go above 40mb/s download if i'm uploading 700/800+ mbit at the same time, which btw is normal for me. But my max speed down and up is ~110mb/s, or ~170mb/s simultaneous before my wan port caps out.
But i have not used manual cache size, i've always left it at auto, and just increased the expiry. Also, i found out it was lib1.1 that caused being stuck at 663mb. Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s. But it didn't want to go above 1.9gb, not sure what's going on there.
Last edited by fusk on Sat Oct 08, 2016 2:01 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
So it seems later versions of libtorrent are more reluctant to use large caches. Probably a good thing, I guess.
"Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s."
Was that with the 64bit version of qBT? Otherwise, it could be the 32bit version was stopping just before a certain 2GB crash. There are ways to make a 32bit Windows app capable of using up to 3 GB ram, but qBT apparently doesn't do that.
The cache does need a longer retention time than 60 seconds default and 600 seconds max. Deluge allows much longer -- over 30,000 seconds. 1 day would be 86,400 seconds.![Tongue :P](./images/smilies/tongue.gif)
1 hour would be 3600 seconds, a reasonable value for use with unusual conditions.
"Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s."
Was that with the 64bit version of qBT? Otherwise, it could be the 32bit version was stopping just before a certain 2GB crash. There are ways to make a 32bit Windows app capable of using up to 3 GB ram, but qBT apparently doesn't do that.
The cache does need a longer retention time than 60 seconds default and 600 seconds max. Deluge allows much longer -- over 30,000 seconds. 1 day would be 86,400 seconds.
![Tongue :P](./images/smilies/tongue.gif)
1 hour would be 3600 seconds, a reasonable value for use with unusual conditions.
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="Switeck"]
So it seems later versions of libtorrent are more reluctant to use large caches. Probably a good thing, I guess.
"Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s."
Was that with the 64bit version of qBT? Otherwise, it could be the 32bit version was stopping just before a certain 2GB crash. There are ways to make a 32bit Windows app capable of using up to 3 GB ram, but qBT apparently doesn't do that.
The cache does need a longer retention time than 60 seconds default and 600 seconds max. Deluge allows much longer -- over 30,000 seconds. 1 day would be 86,400 seconds.![Tongue :P](./images/smilies/tongue.gif)
1 hour would be 3600 seconds, a reasonable value for use with unusual conditions.
[/quote]
Yes, it's 64bit. Even tho it can't use above 1.9gb, at least it's not stuck at 663mb. I've found that 100s seems to fit with 1.9gb. Do you disable OS cache ?
So it seems later versions of libtorrent are more reluctant to use large caches. Probably a good thing, I guess.
"Switching to lib1.0 pushed the auto cache up to 1.9gb even at 150s."
Was that with the 64bit version of qBT? Otherwise, it could be the 32bit version was stopping just before a certain 2GB crash. There are ways to make a 32bit Windows app capable of using up to 3 GB ram, but qBT apparently doesn't do that.
The cache does need a longer retention time than 60 seconds default and 600 seconds max. Deluge allows much longer -- over 30,000 seconds. 1 day would be 86,400 seconds.
![Tongue :P](./images/smilies/tongue.gif)
1 hour would be 3600 seconds, a reasonable value for use with unusual conditions.
[/quote]
Yes, it's 64bit. Even tho it can't use above 1.9gb, at least it's not stuck at 663mb. I've found that 100s seems to fit with 1.9gb. Do you disable OS cache ?
Re: Unofficial 64-bit installer/archive 3.3.x
I've tested with and without the OS cache.
All that seems to change is how quickly windows reports out-of-memory errors.![Tongue :P](./images/smilies/tongue.gif)
(qBT still claims to use about the same amount either way...)
All that seems to change is how quickly windows reports out-of-memory errors.
![Tongue :P](./images/smilies/tongue.gif)
(qBT still claims to use about the same amount either way...)
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="Switeck"]
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
Last edited by fusk on Thu Oct 27, 2016 7:12 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
It only happens if you do what I outlined here:
index.php/topic,1645.msg23572.html#msg23572
index.php/topic,1645.msg23572.html#msg23572
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="fusk"]
[quote="Switeck"]
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
[/quote]
With 3.3.6 and the versions before that I tested, I can set the cache to 4096MiB it will happily gobble up 6GiB of my memory. I have recently gotten another internet upgrade and with even a 600s cache, the hit-rate was not high enough to saturate my connection. I had to switch to using my SSDs.
I actually found that qBittorrent gets very slow as the cache gets larger. A 2x larger cache may take 10x longer before it can close. At 4GiB of data cached, it takes nearly 10 minutes for it to free up the memory, then close. With SSDs, I have limited it to 512MiB of cache and it closes instantly.
[quote="Switeck"]
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
[/quote]
With 3.3.6 and the versions before that I tested, I can set the cache to 4096MiB it will happily gobble up 6GiB of my memory. I have recently gotten another internet upgrade and with even a 600s cache, the hit-rate was not high enough to saturate my connection. I had to switch to using my SSDs.
I actually found that qBittorrent gets very slow as the cache gets larger. A 2x larger cache may take 10x longer before it can close. At 4GiB of data cached, it takes nearly 10 minutes for it to free up the memory, then close. With SSDs, I have limited it to 512MiB of cache and it closes instantly.
Last edited by Henry63 on Fri Oct 28, 2016 10:55 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="Henry63"]
[quote="fusk"]
[quote="Switeck"]
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
[/quote]
With 3.3.6 and the versions before that I tested, I can set the cache to 4096MiB it will happily gobble up 6GiB of my memory. I have recently gotten another internet upgrade and with even a 600s cache, the hit-rate was not high enough to saturate my connection. I had to switch to using my SSDs.
I actually found that qBittorrent gets very slow as the cache gets larger. A 2x larger cache may take 10x longer before it can close. At 4GiB of data cached, it takes nearly 10 minutes for it to free up the memory, then close. With SSDs, I have limited it to 512MiB of cache and it closes instantly.
[/quote]
The problem was that i didn't know you had to set it manually to go over 1.9gb. What makes this a problem, at least with 3.3.7 is that memory usage above 1.9gb is reported as "unknown"
I have 16gb ram, which is the reason i won't mind qbit using more than 1.9gb. Also, because of my internet speed, i have to have the expiry at 40/50s or it'll constantly be full and cause some performance issues.
[quote="fusk"]
[quote="Switeck"]
[...] can waste over 1 GB ram (using >5.5 GB total) if its cache grows large enough.
[/quote]
Which version was that ?
3.3.7 64bit can't go over 1.9gb.
[/quote]
With 3.3.6 and the versions before that I tested, I can set the cache to 4096MiB it will happily gobble up 6GiB of my memory. I have recently gotten another internet upgrade and with even a 600s cache, the hit-rate was not high enough to saturate my connection. I had to switch to using my SSDs.
I actually found that qBittorrent gets very slow as the cache gets larger. A 2x larger cache may take 10x longer before it can close. At 4GiB of data cached, it takes nearly 10 minutes for it to free up the memory, then close. With SSDs, I have limited it to 512MiB of cache and it closes instantly.
[/quote]
The problem was that i didn't know you had to set it manually to go over 1.9gb. What makes this a problem, at least with 3.3.7 is that memory usage above 1.9gb is reported as "unknown"
I have 16gb ram, which is the reason i won't mind qbit using more than 1.9gb. Also, because of my internet speed, i have to have the expiry at 40/50s or it'll constantly be full and cause some performance issues.
Re: Unofficial 64-bit installer/archive 3.3.x
x64 version actually works quite well with those ridiculously fast XMP DDR4s out there.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz) with the same memory module, it would take around 8 minutes for qb to completely exit, in xmp mode it takes around 3 minutes to complete the cycle. It is kind of unexpected. The run time, active speed, cache, memory usage etc is of similar value of cause, but I havnt got alot of samples to proof it either.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz) with the same memory module, it would take around 8 minutes for qb to completely exit, in xmp mode it takes around 3 minutes to complete the cycle. It is kind of unexpected. The run time, active speed, cache, memory usage etc is of similar value of cause, but I havnt got alot of samples to proof it either.
Last edited by gspbeetle on Wed Nov 09, 2016 2:46 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="gspbeetle"]
x64 version actually works quite well with those ridiculously fast XMP DDR4s out there.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz)[...]
[/quote]
You know xmp is just a profile to make the memory run as per manufacturer specs? instead of setting it up manually which would scare people away. xmp is not an oc mode or anything like that. Also, mhz isn't everything, there's a bucketload of sub features for memory that can make them slow.
x64 version actually works quite well with those ridiculously fast XMP DDR4s out there.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz)[...]
[/quote]
You know xmp is just a profile to make the memory run as per manufacturer specs? instead of setting it up manually which would scare people away. xmp is not an oc mode or anything like that. Also, mhz isn't everything, there's a bucketload of sub features for memory that can make them slow.
Last edited by fusk on Wed Nov 09, 2016 10:44 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
[quote="fusk"]
[quote="gspbeetle"]
x64 version actually works quite well with those ridiculously fast XMP DDR4s out there.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz)[...]
[/quote]
You know xmp is just a profile to make the memory run as per manufacturer specs? instead of setting it up manually which would scare people away. xmp is not an oc mode or anything like that. Also, mhz isn't everything, there's a bucketload of sub features for memory that can make them slow.
[/quote]
Yes, manufacturer specified clock, but nevertheless it is still overclocked since the clock is in fact increased.
(In my case, I have to tune up my bclk slightly in order for xmp to run at 2800mhz with my i5-6500)
I know XMP isnt exactly new technology, but it wasn't that cheap and ridiculously fast when we were in the DDR3 era.
And yes, I agree that "mhz isn't everything", that's exactly the reason why I am being surprised by the performance boost it actually outputs.
I didn't really expect it to reduce the shutdown time of qb at all when I bought those memory modules, and these memory are not gamer graded either, they got a rather high CL rating (16).
[quote="gspbeetle"]
x64 version actually works quite well with those ridiculously fast XMP DDR4s out there.
So far, when in profile 1 (2800mhz), it significantly improved the startup time (the time need for the add task windows appear when qb is startup by opening up a .torrent) and shutdown time (the time qb stays at background cleaning up garbage after told to exit) for a client with over 2000 tasks.
When in non-oc mode (2133mhz)[...]
[/quote]
You know xmp is just a profile to make the memory run as per manufacturer specs? instead of setting it up manually which would scare people away. xmp is not an oc mode or anything like that. Also, mhz isn't everything, there's a bucketload of sub features for memory that can make them slow.
[/quote]
Yes, manufacturer specified clock, but nevertheless it is still overclocked since the clock is in fact increased.
(In my case, I have to tune up my bclk slightly in order for xmp to run at 2800mhz with my i5-6500)
I know XMP isnt exactly new technology, but it wasn't that cheap and ridiculously fast when we were in the DDR3 era.
And yes, I agree that "mhz isn't everything", that's exactly the reason why I am being surprised by the performance boost it actually outputs.
I didn't really expect it to reduce the shutdown time of qb at all when I bought those memory modules, and these memory are not gamer graded either, they got a rather high CL rating (16).
Last edited by gspbeetle on Thu Nov 10, 2016 2:29 pm, edited 1 time in total.
Re: Unofficial 64-bit installer/archive 3.3.x
Anyone know if Dayman is working on 3.3.9 64bit ?