Re: [HACKERS] Re: v7.1b4 bad performance
| От | Hiroshi Inoue |
|---|---|
| Тема | Re: [HACKERS] Re: v7.1b4 bad performance |
| Дата | |
| Msg-id | 3A924AC5.8A051949@tpf.co.jp обсуждение исходный текст |
| Ответ на | RE: v7.1b4 bad performance ("Schmidt, Peter" <peter.schmidt@prismedia.com>) |
| Список | pgsql-admin |
Tom Lane wrote:
>
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > I've been suspicious if pgbench is an (unique)
> > appropiriate test case for evaluaing commit_delay.
>
> Of course it isn't. Never trust only one benchmark.
>
> I've asked the Great Bridge folks to run their TPC-C benchmark with both
> zero and small nonzero commit_delay. It will be a couple of days before
> we have the results, however. Can anyone else offer any comparisons
> based on other multiuser benchmarks?
>
I changed pgbench so that different connection connects
to the different database and got the following results.
The results of
pgbench -c 10 -t 100
[CommitDelay=0]
1st)tps = 18.484611(including connections establishing)
tps = 19.827988(excluding connections establishing)
2nd)tps = 18.754826(including connections establishing)
tps = 19.352268(excluditp connections establishing)
3rd)tps = 18.771225(including connections establishing)
tps = 19.261843(excluding connections establishing)
[CommitDelay=1]
1st)tps = 20.317649(including connections establishing)
tps = 20.975151(excluding connections establishing)
2nd)tps = 24.208025(including connections establishing)
tps = 24.663665(excluding connections establishing)
3rd)tps = 25.821156(including connections establishing)
tps = 26.842741(excluding connections establishing)
Regards,
Hiroshi Inoue
В списке pgsql-admin по дате отправления: