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

From Douglas McNaught
Subject Re: Spinlocks, yet again: analysis and proposed patches
Date
Msg-id m2wtll9bvq.fsf@Douglas-McNaughts-Powerbook.local
Whole thread Raw
In response to Re: Spinlocks, yet again: analysis and proposed patches  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Spinlocks, yet again: analysis and proposed patches
List pgsql-hackers
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?

-Doug


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Materialized Views in PostgreSQL
Next
From: Douglas McNaught
Date:
Subject: Re: Spinlocks, yet again: analysis and proposed patches