| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: LWLOCK_STATS |
| Date: | 2012-01-10 09:16:35 |
| Message-ID: | CA+U5nMJJOX4AuASRaumXyfcXwnsj+r59AG-v62=VeH6GSib5fA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 10, 2012 at 12:24 AM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> IIRC, pg_bench is *extremely* write-heavy. There's probably not that many systems that operate that way. I suspect that most OLTP systems read more than they write, and some probably have as much as a 10-1 ratio.
IMHO the main PostgreSQL design objective is doing a flexible, general
purpose 100% write workload. Which is why Hot Standby and
LISTEN/NOTIFY are so important as mechanisms for offloading read
traffic to other places, so we can scale the total solution beyond 1
node without giving up the power of SQL.
So benchmarking write-heavy workloads and separately benchmarking
read-only workloads is more representative.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benedikt Grundmann | 2012-01-10 09:25:42 | Re: Page Checksums |
| Previous Message | Joel Jacobson | 2012-01-10 09:12:33 | Re: Generate call graphs in run-time |