Practical upper limits of pgbench read/write tps with 8.3

From: "Jeffrey Baker" <jwbaker(at)gmail(dot)com>
To: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Practical upper limits of pgbench read/write tps with 8.3
Date: 2008-07-07 21:05:37
Message-ID: fd145f7d0807071405t1bdf4be0j8583fc9965a7719e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I'm spending a third day testing with the ioDrive, and it occurred to
me that I should normalize my tests by mounting the database on a
ramdisk. The results were surprisingly low. On the single 2.2GHz
Athlon, the maximum tps seems to be 1450. This is achieved with a
single connection. I/O rates to and from the ramdisk never exceed
50MB/s on a one-minute average.

With the flash device on the same benchmark, the tps rate is 1350,
meaning that as far as PostgreSQL is concerned, on this machine, the
flash device achieves 90% of the best possible performance.

Question being: what's the bottleneck? Is PG lock-bound?

-jwb

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2008-07-07 22:22:05 Re: Practical upper limits of pgbench read/write tps with 8.3
Previous Message PFC 2008-07-07 17:50:30 Re: Fusion-io ioDrive