Having I/O created faster than the storage is able to cope with generally gets the system at some point. I am not sure I missed it or there is actually nothing, but question is what values have been tested to change? And maybe there is no good value to handle large memory systems and small ones.
Otherwise, yeah, it could be worth adjusting dirty_backround_ration downwards (to start backgroud writeout sooner, though if the percentage is too small on small systems, writes get potentially more fragmented) and move the dirty_ratio up (to get a bigger window until processes start to get waiting for flushed I/O). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/808872 Title: Hung tasks on UEC cloud images with EBS volumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/808872/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
