| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Mike Bresnahan <mike(dot)bresnahan(at)bestbuy(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SMP Read-only Performance |
| Date: | 2010-01-27 00:07:02 |
| Message-ID: | dcc563d11001261607t79636439oa8fdbf94addc0ac4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 26, 2010 at 3:01 PM, Mike Bresnahan
<mike(dot)bresnahan(at)bestbuy(dot)com> wrote:
> During these tests top(1) reported 60-70% idle CPU.
>
> As you see, the TPS remains the same as I increase the number of clients. These
> results make it look like PostgreSQL is single-threaded and not taking advantage
> of the multiple cores. Could someone please explain?
This is more likely a limitation of pgbench and not postgresql. pgsql
9.0 has a multi-threaded pgbench coming with it that should help for
testing these situations.
http://www.depesz.com/index.php/2009/08/26/waiting-for-8-5-multi-threaded-pgbench/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-01-27 00:54:13 | Re: SMP Read-only Performance |
| Previous Message | Craig Ringer | 2010-01-26 23:33:39 | Re: create role in a pl/pgsql trigger |