On Tue, Jan 10, 2012 at 12:24 AM, Jim Nasby <j...@nasby.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
