Re: LWLOCK_STATS - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: LWLOCK_STATS
Date
Msg-id CAHyXU0w4YLcTE20VyJE8dROZMrhR-qsC9G+6G4xPFp47RpzsCQ@mail.gmail.com
Whole thread Raw
In response to Re: LWLOCK_STATS  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: pgsphere
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsphere