pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mindaugas Riauba <mind@bi.lt>
To: pgsql-performance@postgresql.org
Subject: Degrading performance
Date: Mon, 2 Jun 2003 08:33:38 +0300
Message-ID: <005a01c328c8$885b9760$f20214ac@bite.lt> (raw)


  Hello,

  I have table with slowly degrading performance. Table is special is
such way that all its rows are updated every 5 minutes (routers interfaces).
vacuum does not help. vacuum full does but I'd like to avoid it.

  Below I added explain analyze output before and after vacuum full. How
could I make that table not to grow?

  PostgreSQL 7.3.2 on Redhat Linux 7.1.
max_fsm_pages=10000 max_fsm_relations=1000.

  Mindaugas

router_db=# explain analyze select * from ifdata;
                                                QUERY PLAN
----------------------------------------------------------------------------
-------------------------------
 Seq Scan on ifdata  (cost=0.00..4894.76 rows=776 width=133) (actual
time=31.65..1006.76 rows=776 loops=1)
 Total runtime: 1007.72 msec
(2 rows)

router_db=# VACUUM full verbose ifdata;
INFO:  --Relation public.ifdata--
INFO:  Pages 4887: Changed 0, reaped 4883, Empty 0, New 0; Tup 776: Vac
46029, Keep/VTL 0/0, UnUsed 186348, MinLen 130, MaxLen 216; Re-using:
Free/Avail. Space 38871060/15072128; EndEmpty/Avail. Pages 2981/1895.
        CPU 0.33s/0.04u sec elapsed 0.45 sec.
INFO:  Index ifdata_clientid_key: Pages 2825; Tuples 776: Deleted 46029.
        CPU 0.23s/0.32u sec elapsed 1.98 sec.
INFO:  Rel ifdata: Pages: 4887 --> 17; Tuple(s) moved: 776.
        CPU 0.30s/0.35u sec elapsed 1.65 sec.
INFO:  Index ifdata_clientid_key: Pages 2825; Tuples 776: Deleted 776.
        CPU 0.21s/0.04u sec elapsed 0.29 sec.
VACUUM
router_db=# explain analyze select * from ifdata;
                                             QUERY PLAN
----------------------------------------------------------------------------
-------------------------
 Seq Scan on ifdata  (cost=0.00..24.76 rows=776 width=133) (actual
time=0.03..7.53 rows=776 loops=1)
 Total runtime: 8.17 msec
(2 rows)





view thread (5+ messages)  latest in thread

Message-ID: <005a01c328c8$885b9760$f20214ac@bite.lt>
Permalink:  ../005a01c328c8$885b9760$f20214ac@bite.lt/
Also on:    postgresql.org/message-id/005a01c328c8$885b9760$f20214ac@bite.lt

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mind@bi.lt
  Subject: Re: Degrading performance
  In-Reply-To: <005a01c328c8$885b9760$f20214ac@bite.lt>
  References: <005a01c328c8$885b9760$f20214ac@bite.lt>

* 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