Re: Performance monitoring

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance monitoring
Date: 2007-05-12 23:24:51
Message-ID: Pine.GSO.4.64.0705121910010.9615@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sat, 12 May 2007, Joshua D. Drake wrote:

> One thing that doesn't seemed to be being looked at it is the cost of
> logging.

If any of this executed at something like the query level, sure, that
would be real important. The majority of the logging I suggested here is
of things that happen at checkpoint time. The presumption is that the
overhead of that is considerably greater than writing a log line or even
five.

The least intensive event I would like to be loggable is when a new WAL
segment is created and cleared, which is again a pretty small bit of log
compared to the 16MB write. I wouldn't mind seeing that exposed under
pg_stats instead, just had more interesting things to statify first.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2007-05-13 01:32:29 Re: Automatic adjustment of bgwriter_lru_maxpages
Previous Message Greg Smith 2007-05-12 23:09:55 Re: Performance monitoring (was: [PATCHES] Logging checkpoints and other slowdown causes)

Browse pgsql-patches by date

  From Date Subject
Next Message Greg Smith 2007-05-13 01:32:29 Re: Automatic adjustment of bgwriter_lru_maxpages
Previous Message Greg Smith 2007-05-12 23:09:55 Re: Performance monitoring (was: [PATCHES] Logging checkpoints and other slowdown causes)