From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | peter(dot)schmidt(at)prismedia(dot)com, pgsql-hackers(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Re: v7.1b4 bad performance |
Date: | 2001-02-17 06:46:35 |
Message-ID: | 20010217154635M.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
> "Schmidt, Peter" <peter(dot)schmidt(at)prismedia(dot)com> writes:
> > So, is it OK to use commit_delay=0?
>
> Certainly. In fact, I think that's about to become the default ;-)
I agree with Tom. I did some benchmarking tests using pgbench for a
computer magazine in Japan. I got a almost equal or better result for
7.1 than 7.0.3 if commit_delay=0. See included png file.
--
Tatsuo Ishii
Attachment | Content-Type | Size |
---|---|---|
image/png | 4.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-17 06:59:59 | Re: [HACKERS] Re: v7.1b4 bad performance |
Previous Message | Tom Lane | 2001-02-17 06:10:38 | Re: v7.1b4 bad performance |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-17 06:59:59 | Re: [HACKERS] Re: v7.1b4 bad performance |
Previous Message | Tom Lane | 2001-02-17 06:10:38 | Re: v7.1b4 bad performance |