| From: | Mark Wong <markw(at)osdl(dot)org> |
|---|---|
| To: | Douglas McNaught <doug(at)mcnaught(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <marko(at)l-t(dot)ee> |
| Subject: | Re: Spinlocks, yet again: analysis and proposed patches |
| Date: | 2005-09-13 17:32:42 |
| Message-ID: | 200509131733.j8DHX1Bo003723@smtp.osdl.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 13 Sep 2005 12:21:45 -0400
Douglas McNaught <doug(at)mcnaught(dot)org> wrote:
> Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-13 17:38:08 | Re: Spinlocks, yet again: analysis and proposed patches |
| Previous Message | Douglas McNaught | 2005-09-13 17:21:32 | Re: Spinlocks, yet again: analysis and proposed patches |