Skip site navigation (1) Skip section navigation (2)

Re: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...
Date: 2011-02-28 22:05:08
Message-ID: 4D6C1C14.2010909@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> I don't understand what you're talking about at all here. I think
> there are a lot of unsolved problems in monitoring but the one thing I
> think everyone is pretty clear on is that the right way to export
> metrics like these is to export a counter and then have some external
> component periodically copy the counter into some history table and
> calculate the derivative, second derivative, running average of the
> first derivative, etc.

You missed the original point of the discussion, which was to have stats
we could use for auto-tuning internally.  Not to export them.

For example, there are optimizations we could make with the query
planner if we knew which tables and indexes were "hot" in general.
That's how we started this discussion, and it's not solved by storing
the stats history on another server.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

In response to

Responses

pgsql-hackers by date

Next:From: AntonDate: 2011-02-28 22:21:34
Subject: Re: Native XML
Previous:From: Robert HaasDate: 2011-02-28 22:00:59
Subject: Re: SR standby hangs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group