Re: New to PostgreSQL, performance considerations
| От | Tom Lane |
|---|---|
| Тема | Re: New to PostgreSQL, performance considerations |
| Дата | |
| Msg-id | 15642.1166075096@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: New to PostgreSQL, performance considerations ("Joshua D. Drake" <jd@commandprompt.com>) |
| Ответы |
Re: New to PostgreSQL, performance considerations
Re: New to PostgreSQL, performance considerations Re: New to PostgreSQL, performance considerations Re: New to PostgreSQL, performance considerations |
| Список | pgsql-performance |
"Joshua D. Drake" <jd@commandprompt.com> writes:
> On Wed, 2006-12-13 at 18:36 -0800, Josh Berkus wrote:
>> Mostly, though, pgbench just gives the I/O system a workout. It's not a
>> really good general workload.
> It also will not utilize all cpus on a many cpu machine. We recently
> found that the only way to *really* test with pgbench was to actually
> run 4+ copies of pgbench at the same time.
The pgbench app itself becomes the bottleneck at high transaction
rates. Awhile back I rewrote it to improve its ability to issue
commands concurrently, but then desisted from submitting the
changes --- if we change the app like that, future numbers would
be incomparable to past ones, which sort of defeats the purpose of a
benchmark no?
regards, tom lane
В списке pgsql-performance по дате отправления: