From: Tobias Brox <tobias@nordicbet.com>
To: Erik Jones <erik@myemma.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: Joe Healy <joe@omc-international.com.au>
Cc: Dan Harris <fbsd@drivefaster.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: OT: Munin (was Re: Determining server load from client)
Date: Wed, 21 Mar 2007 22:13:05 +0100
Message-ID: <20070321211305.GA29211@oppetid.no> (raw)
In-Reply-To: <2B568D22-BDCC-40B7-B27D-0F47216094F2@myemma.com>
References: <460080A2.20800@drivefaster.net>
<46008931.8060605@omc-international.com.au>
<4600E13F.3070806@archonet.com>
<20070321101340.GI10137@oppetid.no>
<2B568D22-BDCC-40B7-B27D-0F47216094F2@myemma.com>
[Erik Jones - Wed at 09:31:48AM -0500]
> I use cacti (http://cacti.net) which does the same thing that munin
> does but in php instead. Here's what I use to db stats to it (again,
> php):
I haven't tried cacti, but our sysadm has done a little bit of research
and concluded "cacti is better". Maybe some day we'll move over.
Munin is generating all the graphs statically every fifth minute, while
cacti generates them on demand as far as I've understood. The munin
approach is pretty bloat, since one usually would watch the graphs much
more seldom than what they are generated (at least, we do). That's not
really an argument since CPU is cheap nowadays - but a real argument is
that the munin approach is less flexible. One would like to adjust the
graph (like, min/max values for both axis) while watching quite some
times.
> $actives_sql = "SELECT COUNT(*)
> FROM pg_stat_activity
> WHERE current_query NOT ILIKE '<idle>'
> AND now() - query_start > '1 second';";
So this one is quite similar to mine ...
> $db_stat_sql = "SELECT {$argv[2]}
> FROM pg_stat_database
> WHERE datname='$db_name';";
I was not aware of this view - it can probably be useful for us. I will
add this one when I get the time ... (I'm at vacation now).
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: tobias@nordicbet.com, erik@myemma.com, dev@archonet.com, joe@omc-international.com.au, fbsd@drivefaster.net
Subject: Re: OT: Munin (was Re: Determining server load from client)
In-Reply-To: <20070321211305.GA29211@oppetid.no>
* 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