| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, 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 14:10:01 |
| Message-ID: | CAHyXU0w4YLcTE20VyJE8dROZMrhR-qsC9G+6G4xPFp47RpzsCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 10, 2012 at 3:16 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> So benchmarking write-heavy workloads and separately benchmarking
> read-only workloads is more representative.
Absolutely. High write activity applications are much more difficult
to optimize with simple tricks like client side caching. Also,
storage is finally moving out of the dark ages so that high write
transaction rate servers are no longer necessarily i/o bound without
on reasonable hardware.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-01-10 14:28:58 | Re: pgsql: plpython: Add SPI cursor support |
| Previous Message | Dave Cramer | 2012-01-10 14:04:56 | Re: pgsphere |