Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E8C349FB760 for ; Wed, 21 Mar 2007 18:13:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 50688-01 for ; Wed, 21 Mar 2007 18:13:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lynet.oppetid.no (oppetid.no [80.65.51.2]) by postgresql.org (Postfix) with ESMTP id 469829FB49E for ; Wed, 21 Mar 2007 18:13:08 -0300 (ADT) Received: by lynet.oppetid.no (Postfix, from userid 1019) id 255B811A719; Wed, 21 Mar 2007 22:13:05 +0100 (CET) Date: Wed, 21 Mar 2007 22:13:05 +0100 From: Tobias Brox To: Erik Jones Cc: Tobias Brox , Richard Huxton , Joe Healy , Dan Harris , PostgreSQL Performance Subject: Re: OT: Munin (was Re: Determining server load from client) Message-ID: <20070321211305.GA29211@oppetid.no> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2B568D22-BDCC-40B7-B27D-0F47216094F2@myemma.com> Organization: Group Nordicbet User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/300 X-Sequence-Number: 23705 [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 '' > 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).