From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Hannes Dorbath" <light(at)theendofthetunnel(dot)de> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 8.3 synchronous_commit |
Date: | 2008-01-21 22:11:07 |
Message-ID: | 162867790801211411j48e2d435lc7bba2b735ccfe45@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hello
synchronous_commit = off is well for specific load,
try only one connect pgbench ~ it is analogy for database import or
some administrator's work.
Regards
Pavel Stehule
On 21/01/2008, Hannes Dorbath <light(at)theendofthetunnel(dot)de> wrote:
> I might completely misunderstand this feature. Shouldn't
> "synchronous_commit = off" improve performance?
>
> Whatever I do, I find "synchronous_commit = off" to degrade performance.
>
> Especially it doesn't like the CFQ I/O scheduler, it's not so bad with
> deadline. Synthetic load like
>
> pgbench -i -s 10 -U pgsql -d bench && pgbench -t 1000 -c 100 -U pgsql -d
> bench
>
> or the same with scale 100.
>
> Maybe it's just my test box.. single SATA-II drive, XFS on top of LVM.
>
> I'll retry without LVM once I have another drive.. I've seen LVM mess
> with other things in the past.
>
>
> --
> Best regards,
> Hannes Dorbath
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2008-01-21 22:25:30 | Re: 8.3 synchronous_commit |
Previous Message | Hannes Dorbath | 2008-01-21 21:55:16 | 8.3 synchronous_commit |