HDD load (making too much noise)

[siakc]

qBittorrent & operating system versions

Windows 10 Qbt 4.6.6 libtorrent-rasterbar

What is the problem?

It is not really a bug but definitely a problem. I want to lower HDD activity somehow. With the current rate of continous access its life is definitely cut short. Not to mention its sound polution.

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

NA

[HanabishiRecca]

There are options to limit network transfers speeds. I don't think that we could do anything more useful than that.

[siakc]

Some kind of caching and bursting migjt be helpful.

[wind77]

You could:

1. use SSD.
2. stop p2p.
3. sound proof your chassis.

Options are available, it is ur choice.

[siakc]

Please consider practical solutions before posting. SSD will disguise the problem, it won't solve it. I don't think it is good for SSDs either.

The solution is to read big chunks of data and write big chunks instead of issuing read/write command for small chunks.

[shama84]

And a a mitigation is downloading on disk (HDD, not SSD), enable the space pre-allocation in the preferences of QBT to reduce fragmentation :).

[wind77]

Please consider practical solutions before posting. SSD will disguise the problem, it won't solve it. I don't think it is good for SSDs either.

The solution is to read big chunks of data and write big chunks instead of issuing read/write command for small chunks.

Constant read/write op is not good for disk - and yet you wanna do p2p without harming your disk. I dunno what is your expectation then. Any way, have you looked into Preferences > libtorrent section, in particular, Disk IO?

[tn5421]

Realistically, you could increase Disk Cache, Disk cache expiry interval, and Disk queue size, and they might help? I've never had to tweak these settings myself as the defaults are good enough for casually sharing the latest arch linux isos.

edit: maybe coalesce reads/writes could be helpful too?

[huihuimoe]

use a RAM disk can avoid these all problems

[HanabishiRecca]

SSD will disguise the problem, it won't solve it. I don't think it is good for SSDs either.

1. SSDs don't wear on reads at all, so seeding is free.
2. As for writes, if data end up on the disk anyway, it doesn't matter how fast you write. SSD resource is measured in amount of data written (TBW). I.e. if you have an SSD with 100 TBW resource, it doesn't matter you write that 100 terabytes in short bursts or via constant evenly distributed write.
3. As already mentioned above, operating systems do a fairly good job in caching reads and writes. In fact, libtorrent 2.x memory-mapped files mode as is already irritates people by utilizing all available RAM for a read/write cache.

[shama84]

Put all on an RPI with attached disk, headless in the garage or similar place No problem anymore (my setup :p )

[Balls0fSteel]

Is this a troll post? Noise pollution???

1) Only let 1 download run. HDDs make a great noise if they have to seek around. Their performance also tanks. 2) HDDs doing any kind of work does NOT degrade them whatsoever. 3) HDDs in fact consume less than SSDs while doing work. 4) HDDs die from startups and runtime hours. And whenever they feel like it, because HDDs. That's it.

[siakc]

Disk Cache is on auto (-1). I don't know how much is choosen in this mode. There is no documentation for it when I click the question mark. Disk IO read/write mode are set to Enable OS cache which engages normal OS cache. But normal OS cache. I enabled Use piece extent affinity and Send upload piece suggestions. Also set Disk queue size to about 7.5 megabytes which don't think has any effect when set to high values.