From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | justin(at)postgresql(dot)org, merlin(dot)moncure(at)rcsonline(dot)com, pgsql-hackers(at)postgresql(dot)org, pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Changing the default configuration |
Date: | 2003-02-14 04:00:35 |
Message-ID: | 200302132000.35639.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers pgsql-performance |
Tatsuo,
> Sigh. People always complain "pgbench does not reliably producing
> repeatable numbers" or something then say "that's because pgbench's
> transaction has too much contention on the branches table". So I added
> -N option to pgbench which makes pgbench not to do any UPDATE to
> the branches table. But still people continue to complian...
Hey, pg_bench is a good start on a Postgres performance tester, and it's much,
much better than what there was before you came along ... which was nothing.
Thank you again for contributing it.
pg_bench is, however, only a start on a performance tester, and we'd need to
build it up before we could use it as the basis of a PG tuner.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-14 04:14:49 | Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers |
Previous Message | Kevin Brown | 2003-02-14 03:46:46 | Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-14 04:14:49 | Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers |
Previous Message | Tom Lane | 2003-02-14 04:00:02 | Re: location of the configuration files |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-14 04:14:49 | Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers |
Previous Message | Darryl A. J. Staflund | 2003-02-14 03:55:53 | Re: JBoss CMP Performance Problems with PostgreSQL 7.2.3 |