[lkml]   [2002]   [Feb]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Radix-tree pagecache for 2.5
On February 6, 2002 10:37 pm, Rik van Riel wrote:
> On Wed, 6 Feb 2002 wrote:
> > On Wed, Feb 06, 2002 at 09:44:33AM -0200, Rik van Riel wrote:
> > > Once you get over 'dbench 16' or so the whole thing basically
> > > becomes an excercise in how well the system can trigger task
> > > starvation in get_request_wait.
> >
> > It's neat you've identified that bottleneck.
> Umm, there's one thing you need to remember about these
> high dbench loads though.
> They run fastest when you run each of the dbench forks
> sequentially and have the others stuck in get_request_wait.
> This, of course, is completely unacceptable for real-world
> server scenarios, where all users of the server need to be
> serviced fairly.

Right, and as we just discussed on irc, it's a useful effect - only if we
control it, so that stopped or slowed processes do eventually get forcibly
elevated in terms of IO priority so they can make progress, after being sat
upon by more agressive/successful processes long enough. And we can control
this, it's just going to take a few months to get basic issues of IO queues,
RSS accounting, etc. out of the way so we can address it.

The trouble I have with paying a lot of attention to dbench results at this
point is - we're measuring effects of kernel behaviour that is, at this
point, uncontrolled and effectively random. IOW, we're not measuring the
effects that we're interested in just now. If we need to know IO throughput,
we need to use benches that test exactly that, and not other randomly
interacting effects. As they said on Laugh-in many moons ago: 'very
interesting, but useless'.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.055 / U:14.992 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site