Skip site navigation (1) Skip section navigation (2)

Re: Suggested test points for a performance tool?

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Christoffer Lernö <christoffer(at)aegik(dot)com>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Suggested test points for a performance tool?
Date: 2012-11-05 00:08:04
Message-ID: CAGTBQpY3c2HOJRBqNaKqdaQwY=FUR6xc+BsbeHMUKnKy=1iTfA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Nov 5, 2012 at 12:54 AM, Christoffer Lernö
<christoffer(at)aegik(dot)com> wrote:
> • Top Queries - See which queries are being run the most on your server.
> • Top Users - See which users are using your server the most.
> • Top Tables - See which database tables are opened the most.
> • Top States - See which states your database is most busy doing, such as creating temp tables.
> • Top IPs - See which client IPs are using your server the most.

You probably also want to see top *and bottom* indexes, as maintaining
indexes in postgresql not only hurts insert performance, but it also
impairs HOT updates, which makes it much more important to remove
unused indexes than in MySQL.

You have access to lots of statistics for all relations (tables,
indexes and such), which can also help refine your reports.

Personally, I routinely check "long-lived transactions" and the
queries that generate them, as they're a constant pain with MVCC, by
sorting pg_stat_activity by transaction start time, and checking the
first few transaction if they've been started "long ago" (with "long"
varying from application to application)


In response to

pgsql-performance by date

Next:From: SamratDate: 2012-11-05 06:43:04
Subject: DBT-1
Previous:From: Christoffer LernöDate: 2012-11-04 23:54:56
Subject: Suggested test points for a performance tool?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group