On Thu, Oct 08, 2009 at 03:37:39PM -0500, Kevin Grittner wrote:
> Justin T Pryzby wrote:
> > On Thu, Oct 08, 2009 at 10:49:37AM -0700, Joshua D. Drake wrote:
> >> Did your scheduler change between the kernel versions?
> > No, it's deadline for both.
>
> How about write barriers? I had a kernel
Justin T Pryzby wrote:
> On Thu, Oct 08, 2009 at 10:49:37AM -0700, Joshua D. Drake wrote:
>> Did your scheduler change between the kernel versions?
> No, it's deadline for both.
How about write barriers? I had a kernel upgrade which turned them on
for xfs, with unfortunate performance impacts.
On Thu, Oct 08, 2009 at 10:49:37AM -0700, Joshua D. Drake wrote:
> On Thu, 2009-10-08 at 10:44 -0700, Justin T Pryzby wrote:
> > Hi Everyone
> Did your scheduler change between the kernel versions?
No, it's deadline for both.
Justin
--
Sent via pgsql-performance mailing list (pgsql-performance@
On Thu, 2009-10-08 at 10:44 -0700, Justin T Pryzby wrote:
> Hi Everyone
Did your scheduler change between the kernel versions?
> Not sure if sar can provide other data included by vmstat: IO merged
> in/out, {,soft}irq ticks?
>
> Thanks,
> Justin
>
--
PostgreSQL.org Major Contributor
Command
Hi Everyone
On Fri, Oct 02, 2009 at 12:58:12PM -0700, Justin Pryzby wrote:
> When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
> duration increased by 20% from 5 hours to 6. My first attempt at
On Sat, Oct 03, 2009 at 11:31:11PM -0600, Scott Marlowe wrote:
> between these two to te
On Fri, 2 Oct 2009, Justin Pryzby wrote:
When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
duration increased by 20% from 5 hours to 6.
Why 2.6.27 of all versions? It's one of the versions I skipped altogether
as looking like a mess, after CFS broke everything in 2.6.23 I went
On Fri, Oct 2, 2009 at 7:48 PM, Justin Pryzby wrote:
> [I got no response on -general for a few days so I'm trying here]
>
> When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
> duration increased by 20% from 5 hours to 6. My first attempt at
> resolution was to boot with elevator=de
[I got no response on -general for a few days so I'm trying here]
When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
duration increased by 20% from 5 hours to 6. My first attempt at
resolution was to boot with elevator=deadline. However that's
actually the default IO scheduler in bo
Justin Pryzby writes:
> When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
> duration increased by 20% from 5 hours to 6.
Wouldn't be the first time the kernel guys broke something :-(
I think a complaint to your kernel supplier is in order.
In a coincidence, the first item in the c
[I got no response on -general for a few days so I'm trying here]
When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
duration increased by 20% from 5 hours to 6. My first attempt at
resolution was to boot with elevator=deadline. However that's
actually the default IO scheduler in bo
10 matches
Mail list logo
