From: Joshua Berkus <josh@agliodbs.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Peter van Hardenberg <pvh@pvh.ca>
Cc: pgsql-performance@postgresql.org, Scott Marlowe <scott.marlowe@gmail.com>
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Date: Sun, 12 Feb 2012 14:01:59 -0600 (CST)
Message-ID: <873667728.6754.1329076919645.JavaMail.root@mail-1.01.com> (raw)
In-Reply-To: <CAMkU=1zzx96FQssKixaBubYCWw6Msf1E-2C18HYPDuDfSBTqwA@mail.gmail.com>
> Is there an easy and unintrusive way to get such a metric as the
> aggregated query times? And to normalize it for how much work
> happens
> to have been doing on at the time?
You'd pretty much need to do large-scale log harvesting combined with samples of query concurrency taken several times per minute. Even that won't "normalize" things the way you want, though, since all queries are not equal in terms of the amount of data they hit.
Given that, I'd personally take a statistical approach. Sample query execution times across a large population of servers and over a moderate amount of time. Then apply common tests of statistical significance. This is why Heroku has the opportunity to do this in a way that smaller sites could not; they have enough servers to (probably) cancel out any random activity effects.
--Josh Berkus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, jeff.janes@gmail.com, pvh@pvh.ca, scott.marlowe@gmail.com
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
In-Reply-To: <873667728.6754.1329076919645.JavaMail.root@mail-1.01.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox