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

From Josh Berkus
Subject Re: Spinlocks, yet again: analysis and proposed patches
Date
Msg-id 200509130911.03677.josh@agliodbs.com
Whole thread Raw
In response to Re: Spinlocks, yet again: analysis and proposed patches  (Greg Stark <gsstark@mit.edu>)
Responses Re: Spinlocks, yet again: analysis and proposed patches
List pgsql-hackers
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.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Hard drive failure leads to corrupt db
Next
From: Tom Lane
Date:
Subject: Re: bug #1702: nested composite types in plpgsql