Re: Spinlocks, yet again: analysis and proposed patches - Mailing list pgsql-hackers

From Mark Wong
Subject Re: Spinlocks, yet again: analysis and proposed patches
Date
Msg-id 200509131733.j8DHX1Bo003723@smtp.osdl.org
Whole thread Raw
In response to Re: Spinlocks, yet again: analysis and proposed patches  (Douglas McNaught <doug@mcnaught.org>)
List pgsql-hackers
On Tue, 13 Sep 2005 12:21:45 -0400
Douglas McNaught <doug@mcnaught.org> wrote:

> Josh Berkus <josh@agliodbs.com> writes:
> 
> > Tom, All:
> >
> >> It seems to me what you've found is an outright bug in the linux scheduler.
> >> Perhaps posting it to linux-kernel would be worthwhile.
> >
> > For people using this on Linux 2.6, which scheduler are you using?   Deadline 
> > is the recommended one for databases, and does offer significant (+5-8%) 
> > benefits in some heavy-contention environments, at least in OSDL tests.
> 
> I thought 'deadline' was an I/O scheduler, not a CPU scheduler?

Yes, that's correct.  That's an i/o elevator algorithm.

Mark


pgsql-hackers by date:

Previous
From: Douglas McNaught
Date:
Subject: Re: Spinlocks, yet again: analysis and proposed patches
Next
From: Tom Lane
Date:
Subject: Re: Spinlocks, yet again: analysis and proposed patches