pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Jerome Blomart <j.blomart@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pgsql and net-snmp
Date: Thu, 17 Jan 2008 13:08:33 -0600
Message-ID: <dcc563d10801171108m307da0b9t1f9f786951b391ae@mail.gmail.com> (raw)
In-Reply-To: <a47e65680801170943s2d852ec4n76bfa7161692933@mail.gmail.com>
References: <a47e65680801170943s2d852ec4n76bfa7161692933@mail.gmail.com>

On Jan 17, 2008 11:43 AM, Jerome Blomart <j.blomart@gmail.com> wrote:
>
> I am working for a  small company  offering IT services.
> We are in  the acceptance stage  for a  migration of an old UNIX app
> managing a huge load of data.
>
> This acceptance environment is using a VMWARE ESX platform, a jboss as
> application server ( java servlet as client application )
> and a pgsql database. As the developpers knew there will be a lot of data,
> the server specs are quite high...
> ( on RAM space for instance... jboss + pgsql on the same server ).
>
> As it is ... this environement gets poor results ...

You don't mention your I/O subsystem or what type of load you're
putting on your database.

Lots of disks on a fast RAID controller are often needed to get good
db performance.  You can use some kind of system monitoring tool that
will tell you how much wait time you have versus idle versus user CPU
versus system CPU usage.

> How-to monitor pgsql ?

It's a good idea to keep abreast of what's in the logs, especially
ERROR and PANIC type messages.

> - database healthiness ?
> ------------------------------
> For that part i have only google'd  and looked into the pgsql manual (  and
> extracted a "SELECT * from pg_stats" from pgsql ).
> I could use an extraction script that maps selected data into snmp ( as a
> have done for the processes informations ).
> But using such a way to pack pgsql's pg_stats into snmp will include regular
> query to this table.
>
> Is there any performance issues generated by this type of monitoring ?

Of course there's some load, but it's a small table, and generally
speaking this won't be a noticeable load.
Also run occasional vacuum verbose against the main db and email the
output to yourself for review.  Try to keep an eye on how many dead
pages your db is collecting.



view thread (3+ messages)

Message-ID: <dcc563d10801171108m307da0b9t1f9f786951b391ae@mail.gmail.com>
Permalink:  ../dcc563d10801171108m307da0b9t1f9f786951b391ae@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10801171108m307da0b9t1f9f786951b391ae@mail.gmail.com

 · 

reply

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-admin@postgresql.org
  Cc: scott.marlowe@gmail.com, j.blomart@gmail.com
  Subject: Re: pgsql and net-snmp
  In-Reply-To: <dcc563d10801171108m307da0b9t1f9f786951b391ae@mail.gmail.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