Re: LWLOCK_STATS

Merlin Moncure <mmoncure@gmail.com>

From: Merlin Moncure <mmoncure@gmail.com>

To: Simon Riggs <simon@2ndquadrant.com>

Cc: Jim Nasby <jim@nasby.net>, Robert Haas <robertmhaas@gmail.com>, Jeff Janes <jeff.janes@gmail.com>, pgsql-hackers@postgresql.org

Date: 2012-01-10T14:10:01Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Take fewer snapshots.
- d573e239f035 9.2.0 cited
Various micro-optimizations for GetSnapshopData().
- 0d76b60db468 9.2.0 cited

On Tue, Jan 10, 2012 at 3:16 AM, Simon Riggs <simon@2ndquadrant.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