Follow Slashdot stories on Twitter


Forgot your password?

Submission + - The state of linux IO scheduling for desktop? 2

pinkeen writes: I am using linux as my work & play OS for 5+ years. The one thing that constantly drives me mad is its IO scheduling. When I'm copying a large amount of data in the background, everything else slows down to a crawl while the cpu utilization stays at 1-2%. The process which does the actual copying is highly prioritized in terms of I/O. This is completely inacceptable for a desktop OS. I've heard about the efforts of Con Kolivas and his Brainfuck Scheduler, but it's unsupported now and probably incompatible with latest kernels. Is there any way to fix this? How do you deal with this? I have a feeling that if this issue was to be fixed, the whole desktop would become way more snappier, even if you're not doing any heavy IO in the background.
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

The state of linux IO scheduling for desktop?

Comments Filter:
  • Here's the problem. Scheduling READs is fairly easy, but the moment you mix disk writes into the equation everything goes to hell because the drive will instantly return a completion for a write until its internal caches reach whatever their dirty percentage limit is. It's virtually impossible to manage write bandwidth short of turning off the drive's caches and, of course, turning off the caches destroys write performance even under the best of conditions.

    Without some way to query the cache status of the

Machines that have broken down will work perfectly when the repairman arrives.