On Sat, 2009-10-03 at 21:23 +0200, Jens Axboe wrote: > On Sat, Oct 03 2009, Mike Galbraith wrote: > > > So that's pure goodness, at least. > > > > Yeah, but it's a double edged sword, _maybe_ cut too far in the other > > direction. (impression) > > How can it be too fast? IOW, I think you'll have to quantify that > statement :-) Oh boy. It it were perfectly fair, it should be roughly twice the time it takes to load seekily when running solo, which it's exceeded considerably. I'm not complaining mind you, just being a worry wart. Previously the reader was suffering the pains of hell, which the two dinky changes made match my expectations nearly perfectly (1.7 sec is real close to 1.8, which is real close to the 0.9 it takes to get the bugger loaded cold) > > > So far that looks like a winner. The dictator wanted good latency, he's > > > getting good latency. I'll continue working on this on monday, while I'm > > > waiting for delivery of the Trabant. > > > > I'm unsure feel wise. Disk is sounding too seeky, which worries me. > > Care to elaborate on the feel? Seekiness is not good of course, > depending on timing the async delay could cause some skipping back and > forth. But remember that when you don't hear the disk, it could likely > be doing the async IO which will make the disk very quiet (since it's > just a streamed write). The konsole test is bound to cause seeks, when > it's juggling async IO too. Even alone it's likely pretty seeky. So is > the seekiness persistent, or just shortly when starting konsole? It's a huge winner for sure, and there's no way to quantify. I'm just afraid the other shoe will drop from what I see/hear. I should have kept my trap shut and waited really, but the impression was strong. Sorry for making unquantifiable noise. Ignore me. I've been watching/feeling tests for too many hours and hours and hours ;-) -Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
