From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ryan Wexler <ryan(at)iridiumsuite(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: performance on new linux box |
Date: | 2010-07-08 00:39:16 |
Message-ID: | 11690.1278549556@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Ryan Wexler <ryan(at)iridiumsuite(dot)com> writes:
> Postgresql was previously running on a single cpu linux machine with 2 gigs
> of memory and a single sata drive (v8.3). Basically a desktop with linux on
> it. I experienced slow performance.
> So, I finally moved it to a real server. A dually zeon centos machine with
> 6 gigs of memory and raid 10, postgres 8.4. But, I am now experiencing even
> worse performance issues.
I'm wondering if you moved to a kernel+filesystem version that actually
enforces fsync, from one that didn't. If so, the apparently faster
performance on the old box was being obtained at the cost of (lack of)
crash safety. That probably goes double for your windows-box comparison
point.
You could try test_fsync from the Postgres sources to confirm that
theory, or do some pgbench benchmarking to have more quantifiable
numbers.
See past discussions about write barriers in this list's archives for
more detail.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Wultsch | 2010-07-08 00:39:21 | Re: performance on new linux box |
Previous Message | Ryan Wexler | 2010-07-07 23:06:12 | performance on new linux box |