Re: pg_reset_stats + cache I/O % - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: pg_reset_stats + cache I/O %
Date
Msg-id 20060309032337.GW45250@pervasive.com
Whole thread Raw
In response to Re: pg_reset_stats + cache I/O %  ("mcelroy, tim" <tim.mcelroy@bostonstock.com>)
List pgsql-performance
On Wed, Mar 08, 2006 at 01:35:35PM -0500, mcelroy, tim wrote:
> I actually need this info as I was tasked by management to provide it.  Not
> sure if they understand that or not, I do but management does like to see
> how well the system and its components are performing.  Also, I would
> utilize these results to test any cache tuning changes I may make.

What I feared. While monitoring cache hit % over time isn't a bad idea,
it's less than half the picture, which makes fertile ground for
optimizing for some mythical target instead of actual system
performance. If the "conclusion" from these numbers is that
shared_buffers needs to get set larger than min(50000, 10% of memory)
I'd very seriously re-consider how performance tuning is being done.

But hopefully I'm just being paranoid and you guys are just doing a
great job of monitoring things and keeping on the ball. :)
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-performance by date:

Previous
From: Gorshkov
Date:
Subject: embedded postgres and threading
Next
From: Javier Somoza
Date:
Subject: pgCluster and postgres 8.1