A question - is it possible to have something like the CPU token mechanism, but for IO operations (f.e. hdd-s) ? I have a problem where one of the contexts is really heavy on IO and I'd try to limit that. The scheduler is CFQ, but that does not help much on itself, it's not the scheduling itself that is the problem - if the HDD activity is high, an another context, running apaches will slow down serving files. Running out of children bc of the slowdown apache will start forking new processes to fullfill the incoming demands, this however triggers swapping after running out of ram which in turn makes everything even slower, starting a nasty IO bound load spiral. To make things (maybe) even harder, the IO intensive context is not actually reading/writing all that much data but rather seeking among small blocks of it. Is there a recommended/usual way of solving IO bound problems among vservers ? Putting in CPU limits or tokens does not help as the CPU-s are spending their time on idle or waiting even now so they are always full of tokens.
_______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
