Torrents slow to a crawl after only a few minutes of fast downloading #13314
Comments
|
@marcmy Can't reproduce. For best performance, you should set Async I/O threads to 8 if you're downloading to HDDs, or 4 times the number of CPU cores if using an SSD. Disk cache can be set to auto. Everything else as default settings is fine. |
FranciscoPombal
added
Can't reproduce
|
Thanks, I will try 8 async threads. What cache settings would you recommend
for my configuration?
Ryzen 5 3600 (6c/12t)
32gb ddr4 ram
Seagate 8tb 5400 rpm 256mb cache
…On Wed, Sep 2, 2020, 6:40 PM Francisco Pombal ***@***.***> wrote:
@marcmy <https://github.com/marcmy> Can't reproduce. For best
performance, you should set Async I/O threads to 8 if you're downloading to
HDDs, or 4 times the number of CPU cores if using an SSD.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73S3L64ETATUXQ53PL3SD3CW7ANCNFSM4QTBLQYA>
.
|
|
What the disk activity % in task manager when you face this problem? |
OK will do, I'm moving a bunch of data atm so it might be a while before I can get any accurate readings. |
|
Like I said before, set disk cache to
Oof, is that one of those Seagate drives marketed as "Archive drives"? What is the specific model number (Seagate model numbers are typically something like STXXXXXXXXXX)? If it is one such archive drive, that is a problem, because it uses a technology called SMR (Shingled Magnetic Recording), which has really bad sustained write performance, especially if writes have a non-sequential pattern (as is typically the case with torrents) and also if the drive happens to write to regions near other exsiting files. The pattern you're observing where speed tanks to next to nothing after a while seems to be consistent with patterns observed in SMR drives in similar workflows. Also 5400rpm is slow, and you'll only ever be able to sustain respectable speeds on hard drives (10's/100's of MiB/s) as long as you're only downloading 1 or 2 torrents at the same time and with "Download pieces in sequential order". |
|
It's an ST8000DM004-2CX188. seagate barracuda. I don't think it's an
archive drive, and surprisingly the drive performs better in benchmarks
than my other two 7200 rpm drives. Maybe that's due to their age and wear
and tear. I have not specifically checked for sustained writes or anything.
I'll look into that after I'm done copying, as well as the stats.
…On Thu, Sep 3, 2020, 12:52 PM Francisco Pombal ***@***.***> wrote:
@marcmy <https://github.com/marcmy>
Like I said before, set disk cache to auto. Though that typically
overshoots with such high amounts of RAM, so if you want to save a little
RAM, 256 MiB or even 128 MiB will be enough to not cause a performance
bottleneck, while wasting little to no RAM as useless excessive cache.
Seagate 8tb 5400 rpm 256 mb cache
Oof, is that one of those Seagate drives marketed as "Archive drives"?
What is the specific model number (Seagate model numbers are typically
something like STXXXXXXXXXX)?
If it is one such archive drive, that is a problem, because it uses a
technology called SMR (Shingled Magnetic Recording), which has really bad
sustained write performance, especially if writes have a non-sequential
pattern (as is typically the case with torrents) and also if the drive
happens to write to regions near other exsiting files. The pattern you're
observing where speed tanks to next to nothing after a while seems to be
consistent with patterns observed in SMR drives in similar workflows. Also
5400rpm is slow, and you'll only ever be able to sustain respectable speeds
on hard drives (10's/100's of MiB/s) as long as you're only downloading 1
or 2 torrents at the same time and with "Download pieces in sequential
order".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73TADLHHMYQ55Y5XJWLSD7CTFANCNFSM4QTBLQYA>
.
|
|
|
Rip. Okay, time to return.
…On Thu, Sep 3, 2020, 10:24 PM C0RE ***@***.***> wrote:
It's an ST8000DM004-2CX188. seagate barracuda. I don't think it's an
archive drive, and surprisingly the drive performs better in benchmarks
than my other two 7200 rpm drives. Maybe that's due to their age and wear
and tear. I have not specifically checked for sustained writes or anything.
I'll look into that after I'm done copying, as well as the stats.
… <#m_-8580593213082571545_>
On Thu, Sep 3, 2020, 12:52 PM Francisco Pombal *@*.***> wrote: @marcmy
<https://github.com/marcmy> https://github.com/marcmy Like I said before,
set disk cache to auto. Though that typically overshoots with such high
amounts of RAM, so if you want to save a little RAM, 256 MiB or even 128
MiB will be enough to not cause a performance bottleneck, while wasting
little to no RAM as useless excessive cache. Seagate 8tb 5400 rpm 256 mb
cache Oof, is that one of those Seagate drives marketed as "Archive
drives"? What is the specific model number (Seagate model numbers are
typically something like STXXXXXXXXXX)? If it is one such archive drive,
that is a problem, because it uses a technology called SMR (Shingled
Magnetic Recording), which has really bad sustained write performance,
especially if writes have a non-sequential pattern (as is typically the
case with torrents) and also if the drive happens to write to regions near
other exsiting files. The pattern you're observing where speed tanks to
next to nothing after a while seems to be consistent with patterns observed
in SMR drives in similar workflows. Also 5400rpm is slow, and you'll only
ever be able to sustain respectable speeds on hard drives (10's/100's of
MiB/s) as long as you're only downloading 1 or 2 torrents at the same time
and with "Download pieces in sequential order". — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#13314 (comment)
<#13314 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAG73TADLHHMYQ55Y5XJWLSD7CTFANCNFSM4QTBLQYA
.
[image: {9B8441A9-20BA-40C1-B462-61EF836421AA}]
<https://user-images.githubusercontent.com/5726473/92192483-a5a95880-ee98-11ea-9fe8-23f32fdb7437.png>
It's SMR harddisk lol
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73TFHTUU7US6R3O3AYDSEBFW5ANCNFSM4QTBLQYA>
.
|
|
Something you can try is making a LARGE ramdrive (like 10+ GB size) and downloading first to there and having qBitTorrent move to your hard drive/s on completion of the torrents. Obviously will only work if your downloads fit in the ramdrive, so some really large downloads will need to be to a non-SMR HDD. |
|
Torrenting with SMR drives is generally a bad idea. It is one of the use cases in which they can perform really bad. SMR drives are designed for a "write sequentially infrequently, read many times" type of workflow - not the case for torrenting, NAS RAID arrays, etc. HDD manufacturers have been caught hiding the underlying technology used in their drives, ultimately resulting in lawsuits filed against them. Unfortunately, if you want a non-SMR drive, you'll have to pay for it. There are no cheap 8 TB non-SMR drives. Fortunately, due to the controversy, the big 3 manufacturers (Seagate, WD, Toshiba) have now published information detailing exactly which model numbers are SMR. Be sure to know what you're in for when buying hard drives. Further reading: Your experience will definitely improve with a non-SMR drive. That being said, as a disclaimer, at this point we can't be sure it will fix all your problems. Good luck! |
|
Thanks for the info! Should have suspected the 8tb was too good to be true
for that price. I am ok with paying more for a non-SMR drive, or I will get
a 6tb instead.
…On Fri, Sep 4, 2020, 5:22 AM Francisco Pombal ***@***.***> wrote:
@marcmy <https://github.com/marcmy>
Torrenting with SMR drives is generally a bad idea. It is one of the use
cases in which they can perform really bad. SMR drives are designed for a
"write sequentially infrequently, read many times" type of workflow - not
the case for torrenting, NAS RAID arrays, etc. HDD manufacturers have been
caught hiding the underlying technology used in their drives, ultimately
resulting in lawsuits filed against them. Unfortunately, if you want a
non-SMR drive, you'll have to pay for it. There are no cheap 8 TB non-SMR
drives. Fortunately, due to the controversy, the big 3 manufacturers
(Seagate, WD, Toshiba) have now published information detailing exactly
which model numbers are SMR. Be sure to know what you're in for when buying
hard drives.
Further reading:
https://www.servethehome.com/surreptitiously-swapping-smr-into-hard-drives-must-end/
https://arstechnica.com/information-technology/2020/06/lawsuit-vs-western-digital-wants-to-end-any-use-of-smr-in-nas-drives/
https://www.tomshardware.com/news/wd-lists-all-drives-slower-smr-techNOLOGY
Your experience will definitely improve with a non-SMR drive. That being
said, as a disclaimer, at this point we can't be sure it will fix all your
problems. Good luck!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73VNCFCFCCCLX6AW2QLSECWTTANCNFSM4QTBLQYA>
.
|
|
Seeding torrents off a SMR HDD should be fast enough though, so long as they're not significantly fragmented (files-wise). |
|
@Seeker2 If you are only seeding it's fine (still probably not so good performance, especially with many simultaneously active torrents because it's a hard drive, after all), but OP specifically states they observe the performance problem when downloading. |
|
Yes, I agree that downloading performance is awful on SMR HDDs. Even getting files onto the SMR HDD for seeding in any manner can be problematic. |
|
Update... I've finally gotten myself a new non-SMR drive, found a really
nice deal on a WD Easystore 14 TB. Everywhere I looked said it was the best
performance/value and was CMR, despite being 5400 rpm should not have any
issues with writes. I copied everything from the 8 TB Seagate overnight and
it was going 145-155 MB/s which is WAY faster than copying to the Seagate
which was around 30 MB/s. However, now my issue seems to be even worse than
before when downloading torrents to this new drive. It's almost not
downloading at all, whereas on the other drive it did some for a while
before it stopped and then had spikes. My speed graph/stats:
https://i.imgur.com/FpExyFJ.png - My disk activity in Task manager is 100%
for this drive the entire time and it is writing consistently around 125
MB/s. I can't understand how it could write 125 MB/s for hours on end when
it only downloaded a few GB. What is even being written? The actual space
on the drive doesn't seem to be changing significantly during this time. I'm at a total
loss here.
My drive btw:
https://i.imgur.com/5UhXkuX.png
…On Fri, Sep 4, 2020 at 10:22 PM Seeker2 ***@***.***> wrote:
Yes, I agree that downloading performance is awful on SMR HDDs.
Even getting files onto the SMR HDD for seeding in any manner can be
problematic.
A bulk copy of 10 GB of files (1-file-at-a-time!) to a SMR HDD will
probably choke something awful once the SMR HDD runs out of its limited
non-SMR space.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73V6LYTH74T5Y7HSKL3SEGOGDANCNFSM4QTBLQYA>
.
|
|
@marcmy Very strange. Please post logs and settings in plain text. You're using the 64-bit version, correct? You could also try one of these recent experimental builds ( |
|
ok, thanks, will do asap. Yes 64-bit version. I should also note that moving torrents from one
location to another takes forever. I set a temp folder on a different drive
and I checked the write speed to the destination drive and it was between
4.2 and 8.4 MB/s. I'm currently copying with fastcopy at 135 MB/s. It just
seems that overall disk I/O within the program is having major issues.
Here are my settings first:
[Preferences]
Downloads\NewAdditionDialog=false
Bittorrent\MaxUploadsPerTorrent=-1
Scheduler\start_time=@variant(\0\0\0\xf\x1\xb7t\0)
Downloads\DblClOnTorDl=1
Advanced\AnnounceToAllTrackers=true
General\HideZeroComboValues=0
General\NoSplashScreen=true
Downloads\DblClOnTorFn=2
MailNotification\req_auth=false
Connection\GlobalDLLimitAlt=1
Advanced\confirmRemoveAllTags=true
General\CloseToTray=true
General\MinimizeToTray=false
Downloads\SavePath=A:/lulz/
Advanced\trackerPort=9000
Advanced\RecheckOnCompletion=false
Connection\ResolvePeerCountries=true
Connection\PortRangeMin=65135
MailNotification\req_ssl=false
Connection\GlobalDLLimit=0
Connection\InterfaceName=
Advanced\confirmTorrentRecheck=true
Downloads\StartInPause=true
Advanced\IncludeOverhead=true
WebUI\Enabled=false
General\CustomUIThemePath=C:/Program Files/qBittorrent/qbt-theme-master/darkstylesheet.qbtheme
General\PreventFromSuspendWhenDownloading=false
Advanced\osCache=true
Connection\ResolvePeerHostNames=false
General\UseCustomUITheme=true
State\hSplitterSizes=108, 672
Downloads\DiskWriteCacheSize=-1
Downloads\SaveResumeDataInterval=5
General\ExitConfirm=false
MailNotification\enabled=false
Scheduler\days=0
MailNotification\email=
Bittorrent\MaxConnecs=-1
Downloads\NewAdditionDialogFront=true
MailNotification\smtp_server=smtp.changeme.com
Bittorrent\MaxUploads=-1
MailNotification\password=
Advanced\DisableRecursiveDownload=false
Downloads\TempPath=B:/lulz/
Downloads\PreAllocation=false
Scheduler\end_time=@variant(\0\0\0\xf\x4J\xa2\0)
General\Locale=en
Connection\Interface=
General\SystrayEnabled=true
General\AlternatingRowColors=true
Downloads\TempPathEnabled=false
MailNotification\sender=qBittorrent_notification@example.com
Queueing\QueueingEnabled=false
General\HideZeroValues=false
MailNotification\username=
General\StartMinimized=false
Connection\GlobalUPLimitAlt=1
Downloads\ScanDirsLastPath=C:/Users/marcm/Downloads
General\PreventFromSuspendWhenSeeding=false
Advanced\AnonymousMode=true
Downloads\ScanDirsV2=@variant(\0\0\0\x1c\0\0\0\x1\0\0\0\x30\0\x43\0:\0/\0U\0s\0\x65\0r\0s\0/\0m\0\x61\0r\0\x63\0m\0/\0\x44\0o\0w\0n\0l\0o\0\x61\0\x64\0s\0\0\0\x2\0\0\0\x1)
Advanced\updateCheck=true
Connection\alt_speeds_on=true
Advanced\confirmTorrentDeletion=true
State\size=@SiZe(811 1078)
Downloads\DiskWriteCacheTTL=60
Advanced\TrayIconStyle=0
Bittorrent\MaxConnecsPerTorrent=-1
Downloads\UseIncompleteExtension=true
Downloads\TorrentExportDir=A:/torrents
[BitTorrent]
Session\SendBufferLowWatermark=10000
Session\CoalesceReadWrite=true
OSMemoryPriority=BelowNormal
Session\DisableAutoTMMByDefault=false
Session\SendBufferWatermark=100000
Session\SendBufferWatermarkFactor=150
Session\MultiConnectionsPerIp=true
Session\PieceExtentAffinity=false
Session\AsyncIOThreadsCount=8
Session\FilePoolSize=40
Session\DisableAutoTMMTriggers\DefaultSavePathChanged=false
Session\SuggestMode=false
Session\CheckingMemUsageSize=1024
Session\DisableAutoTMMTriggers\CategorySavePathChanged=false
Session\SubcategoriesEnabled=true
[TrackerEntriesDialog]
Dimension=@SiZe(506 500)
[MainWindow]
geometry=@bytearray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\a\x7f\xff\xff\xfe\x9b\0\0\x11\x80\0\0\x4%\0\0\t\xc8\xff\xff\xfe\xc2\0\0\rY\0\0\0\xf4\0\0\0\x1\x2\0\0\0\n\0\0\0\a\x80\xff\xff\xfe\xba\0\0\x11\x7f\0\0\x4$)
qt5\vsplitterState=@bytearray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x1\x1b\0\0\b\xc8\x1\xff\xff\xff\xff\x1\0\0\0\x1\0)
[Application]
FileLogger\Age=1
FileLogger\DeleteOld=true
FileLogger\AgeType=1
FileLogger\Path=C:/Users/marcm/AppData/Local/qBittorrent/logs
FileLogger\Enabled=true
FileLogger\Backup=true
FileLogger\MaxSizeBytes=66560
[SpeedWidget]
graph_enable_7=false
graph_enable_6=false
Enabled=true
graph_enable_0=true
graph_enable_3=false
graph_enable_2=false
period=3
graph_enable_1=true
graph_enable_5=false
graph_enable_9=false
graph_enable_8=false
graph_enable_4=false
[AutoRun]
enabled=false
ConsoleEnabled=false
program=
[CookiesDialog]
CookiesViewState=@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x2'\0\0\0\x5\x1\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x5\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x97\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\0\0\0\x64)
Size=@SiZe(618 369)
[AddNewTorrentDialog]
SplitterState=@bytearray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x1L\0\0\x1\0\0\xff\xff\xff\xff\x1\0\0\0\x1\0)
DialogSize=@SiZe(900 625)
qt5\treeHeaderState="@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x6\x34\0\0\0\x3\0\0\0\x2\0\0\0\x64\0\0\0\x5\0\0\0\x64\0\0\0\x4\0\0\0\x64\0\0\x1,\0\0\0\x6\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x6\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)"
RememberLastSavePath=false
[TorrentProperties]
Peers\qt5\PeerListState=@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x6\x1\0\0\0\0\0\0\0\0\0\0\0\xe\0 \0\0\0\x1\0\0\0\r\0\0\0\x64\0\0\x5N\0\0\0\xe\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\xe\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x9e\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)
CurrentTab=5
SplitterSizes="767,480"
Visible=true
Trackers\qt5\TrackerListState=@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x3 \0\0\0\b\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\b\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\0\0\0\x64)
qt5\FilesListState=@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x3\x80\0\0\0\x6\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x6\0\0\x1\x8c\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)
[GUI]
Log\Types=-1
DownloadTrackerFavicon=true
Log\Enabled=true
Notifications\TorrentAdded=true
Notifications\Enabled=true
[TransferListFilters]
CategoryFilterState=true
selectedFilterIndex=0
[PreviewSelectDialog]
Dimension=@SiZe(462 256)
HeaderState=@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x4\b\0\0\0\x1\0\0\0\x3\0\0\0\x64\0\0\x1\xd0\0\0\0\x4\x1\x1\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x4\0\0\x1\b\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\0\0\0\x64)
[LegalNotice]
Accepted=true
[ShutdownConfirmDlg]
DontConfirmAutoExit=false
[RSS]
AutoDownloader\DownloadRepacks=true
AutoDownloader\SmartEpisodeFilter=s(\\d+)e(\\d+), (\\d+)x(\\d+), "(\\d{4}[.\\-]\\d{1,2}[.\\-]\\d{1,2})", "(\\d{1,2}[.\\-]\\d{1,2}[.\\-]\\d{4})"
[TransferList]
qt5\HeaderState="@bytearray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\xe\x1\0\0\0\x1f\0\0\0\0\0\0\0\x1\0\0\0\x2\0\0\0\x3\0\0\0\x4\0\0\0\x5\0\0\0\b\0\0\0\t\0\0\0\x6\0\0\0\a\0\0\0\n\0\0\0\v\0\0\0\f\0\0\0\r\0\0\0\xe\0\0\0\xf\0\0\0\x10\0\0\0\x11\0\0\0\x12\0\0\0\x13\0\0\0\x14\0\0\0\x15\0\0\0\x16\0\0\0\x17\0\0\0\x18\0\0\0\x19\0\0\0\x1a\0\0\0\x1b\0\0\0\x1c\0\0\0\x1d\0\0\0\x1e\0\0\0\x1f\0\0\0\0\0\0\0\x1\0\0\0\x2\0\0\0\x3\0\0\0\x4\0\0\0\x5\0\0\0\b\0\0\0\t\0\0\0\x6\0\0\0\a\0\0\0\n\0\0\0\v\0\0\0\f\0\0\0\r\0\0\0\xe\0\0\0\xf\0\0\0\x10\0\0\0\x11\0\0\0\x12\0\0\0\x13\0\0\0\x14\0\0\0\x15\0\0\0\x16\0\0\0\x17\0\0\0\x18\0\0\0\x19\0\0\0\x1a\0\0\0\x1b\0\0\0\x1c\0\0\0\x1d\0\0\0\x1e\0\0\0\x1f\x1\x4\xe6=\0\0\0\f\0\0\0\0\0\0\0\x64\0\0\0\x11\0\0\0\x64\0\0\0\x12\0\0\0\x64\0\0\0\x15\0\0\0\x64\0\0\0\x16\0\0\0\x64\0\0\0\x17\0\0\0\x64\0\0\0\x18\0\0\0\x64\0\0\0\x1a\0\0\0\x64\0\0\0\n\0\0\0\x64\0\0\0\x1b\0\0\0\x64\0\0\0\x1c\0\0\0\x64\0\0\0\x1d\0\0\0\x64\0\0\b\x8d\0\0\0\x1f\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x1f\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x2\x15\0\0\0\x1\0\0\0\0\0\0\0H\0\0\0\x1\0\0\0\0\0\0\0U\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0Z\0\0\0\x1\0\0\0\0\0\0\0Q\0\0\0\x1\0\0\0\0\0\0\0X\0\0\0\x1\0\0\0\0\0\0\0:\0\0\0\x1\0\0\0\0\0\0\0\x45\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x35\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0S\0\0\0\x1\0\0\0\0\0\0\0\x80\0\0\0\x1\0\0\0\0\0\0\0\x82\0\0\0\x1\0\0\0\0\0\0\0\x86\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0U\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x84\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x44\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\0\0\0\x64)"
…On Mon, Sep 14, 2020 at 7:59 PM Francisco Pombal ***@***.***> wrote:
@marcmy <https://github.com/marcmy> Very strange. Please post logs and
settings in plain text. You're using the 64-bit version, correct? You could
also try one of these recent experimental builds (master commit 1c87073
<1c87073>):
https://github.com/FranciscoPombal/qBittorrent/actions/runs/241080799
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73XV35OXTAOFD6LC3ATSF2U4HANCNFSM4QTBLQYA>
.
|
|
@marcmy Your configuration includes some potentially problematic choices, like |
|
Great news! Major breakthrough. I recalled an issue I had on another system
where disk usage was at 100% anytime the disk was being used. The culprit
was "MSI mode" in Windows. Being that my disk was at 100% usage during any
downloading, I decided to test to see if that was the cause. First I
shucked my new external drive (removed it from the outer casing and
installed it in my PC) which I had planned to do from the start, and
disabled MSI mode on my SATA controllers. The result? I am now downloading
8 torrents simultaneously at my maximum connection speed for the past 10
minutes! My disk usage is no longer 100% and is instead showing the correct
percentage of use. My write cache is no longer overloaded, and there are no
queued I/O jobs. My issues are completely resolved! Thank you very much for
the help Francisco.
My speed graph:
https://i.imgur.com/lxd22Ep.png
If anyone else has an issue similar the one I had, try disabling MSI mode.
Instructions to do so are here:
https://support.microsoft.com/en-us/help/3083595/task-manager-might-show-100-disk-utilization-on-windows-10-devices-wit
And remember to research your drives before you buy them (stay away from
SMR).
Thanks again for the help.
…On Tue, Sep 15, 2020 at 2:45 PM Francisco Pombal ***@***.***> wrote:
@marcmy <https://github.com/marcmy> Your configuration includes some
potentially problematic choices, like Downloads\SaveResumeDataInterval=5.
This is typically too frequent, and it may be impacting negatively your
disk performance for all other tasks. I would suggest trying to reproduce
this issue with all default settings (backup
C:\Users\<username>\AppData\Roaming\qBittorrent and delete it from the
original location to easily reset all settings to defaults) except for
async I/O set to 8, disk cache to auto, and file pool size to 4000. If you
still get the same results, try with anti-virus disabled.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAG73TIBLSE75HVSWSJBTLSF6Y55ANCNFSM4QTBLQYA>
.
|
|
@marcmy Thanks for the troubleshooting information. Hopefully this information can also help others having issues with external drives. |
FranciscoPombal
added
Not an issue
Please provide the following information
qBittorrent version and Operating System
4.2.5 / Windows 10
What is the problem
After only a few minutes of downloading (normally) on my 1Gbps Fiber connection, all torrents basically come to a stop, downloading at a mere KB/s or B/s, with some spikes here and there. I have tried using 3 different drives, experimented with different cache settings, along with the other advanced options. Nothing seems to work here. I've tried everything at this point. I replaced one of the drives due to poor benchmark speed, and the new drive is having the same issue. I'm not even downloading that fast, maybe 50-60MB/s, I don't know what could cause the drive to not be able to keep up.
What is the expected behavior
I expect qBittorrent to continue downloading normally and slow down if it absolutely needs to. However, it ends up slowing/stopping the downloads for HOURS, until I restart the program. This can't be normal.
Extra info(if any)
I have 32gb ram and even experimented with using ALL of it as cache, which let me download for longer, but not by much. Not sure where to go from here.
The text was updated successfully, but these errors were encountered: