|
|
Log in / Subscribe / Register

The pernicious USB-stick stall problem

The pernicious USB-stick stall problem

Posted Nov 9, 2013 6:58 UTC (Sat) by Nagilum (guest, #93411)
Parent article: The pernicious USB-stick stall problem

This has been bugging me for years and my solution has almost always been:
vm.dirty_background_ratio=0
or some other very low number (0..5). Personally I see no reason to delay starting to write dirty data out other than power saving. There is usually only a very slim chance that data will be written that will be deleted right away again so delaying starting to flush the data to disk makes very little sense to me.
If you have multiple writers it may also help with the performance if you have a higher value here but high for me is something like 5.


to post comments

The pernicious USB-stick stall problem

Posted Nov 15, 2013 13:40 UTC (Fri) by Wol (subscriber, #4433) [Link] (1 responses)

> There is usually only a very slim chance that data will be written that will be deleted right away again

You're obviously not a developer (or gentoo user). I have a huge (20/30Gb ramdisk) for temp precisely because I quite often have gigs of data that gets created and deleted pretty quick. What's the point of writing it to disk when my system has plenty of ram?

Cheers,
Wol

The pernicious USB-stick stall problem

Posted Nov 15, 2013 14:03 UTC (Fri) by Nagilum (guest, #93411) [Link]

That's right I'm not a full time developer.
Anyway if nothing else is waiting for IO on that disk then it still wouldn't bother you very much since it won't block anything.
Anyhow you have your use-case solved.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds