https://bugs.kde.org/show_bug.cgi?id=356357
--- Comment #6 from Riku Voipio <nc...@kos.to> --- (In reply to kdeu from comment #5) > https://linux.die.net/man/1/ionice > Baloo's priority is set to Idle, which means it should not cause "abusive" > disk activity. ionice is being used, and it does a good job to makes sure the crawling activity happens at lower priority than other use. The effect of ionice is ruined by aggressive fdatasync usage when writing the large LMDB database. It appears fdatasync causes disk writes from a kernel thread that has collected all buffered disk writes. Buffers don't carry the iopriority info on them. Kernel thread just sees the red flag "please commit this data ASAP" and then thinks "to keep FS consistent, I should also commit lots of other unwritten pages just to be sure". Try the patch I made. The disk light still flashes like mad but it doesn't ruin interactive use anymore. Iopriority works as expected until you ask the kernel to be sure writes get to disk too. (In reply to kdeu from comment #3) > I'm not sure if I should keep this bug open or what. Specially since this is > probably only a problem during first run. It also appears when doing operations like switching branches in huge git trees (linux, chromium), copying directories etc. -- You are receiving this mail because: You are watching all bug changes.
