Getting time-dependent load statistics
Hall�chen!
Yesterday I ported a web app to PG. Every 10 minutes, a cron job
scanned the log files of MySQL and generated a plot showing the
queries/sec for the last 24h. (Admittedly queries/sec is not the
holy grail of DB statistics.)
But I still like to have something like this. At the moment I just
do the same with PG's log file, with
log_statement_stats = on
But to generate these plots is costly (e.g. I don't need all the
lines starting with !), and to interpret them is equally costly. Do
you have a suggestion for a better approach?
Tsch�,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bronger@jabber.rwth-aachen.de
On Fri, 20 Feb 2009, Torsten Bronger wrote:
Hall�chen!
Yesterday I ported a web app to PG. Every 10 minutes, a cron job
scanned the log files of MySQL and generated a plot showing the
queries/sec for the last 24h. (Admittedly queries/sec is not the
holy grail of DB statistics.)But I still like to have something like this. At the moment I just
do the same with PG's log file, withlog_statement_stats = on
But to generate these plots is costly (e.g. I don't need all the
lines starting with !), and to interpret them is equally costly. Do
you have a suggestion for a better approach?
Have a look at http://pgfouine.projects.postgresql.org/
Hall�chen!
Torsten Bronger writes:
Yesterday I ported a web app to PG. Every 10 minutes, a cron job
scanned the log files of MySQL and generated a plot showing the
queries/sec for the last 24h. (Admittedly queries/sec is not the
holy grail of DB statistics.)But I still like to have something like this.
Sorry, this got posted twice because the mod has a long time lag and
I thought that it was lost.
Tsch�,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bronger@jabber.rwth-aachen.de
Torsten Bronger wrote:
Hall�chen!
Yesterday I ported a web app to PG. Every 10 minutes, a cron job
scanned the log files of MySQL and generated a plot showing the
queries/sec for the last 24h. (Admittedly queries/sec is not the
holy grail of DB statistics.)But I still like to have something like this. At the moment I just
do the same with PG's log file, withlog_statement_stats = on
But to generate these plots is costly (e.g. I don't need all the
lines starting with !), and to interpret them is equally costly. Do
you have a suggestion for a better approach?Tsch�,
Torsten.
If I understood you correctly you might get help from following:
http://pgfouine.projects.postgresql.org/
With Regards
Ashish Karalkar