From: Josh Berkus <josh@agliodbs.com>
To: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Fri, 17 Oct 2003 09:36:25 -0700
Message-ID: <200310170936.25997.josh@agliodbs.com> (raw)
In-Reply-To: <16272.4154.489000.227676@gargle.gargle.HOWL>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<3F9006BF.40906@persistent.co.in>
<16272.4154.489000.227676@gargle.gargle.HOWL>
Rob,
> vacuum_mem might be slowing down the system? But if I reduce it,
> won't vacuuming get slower?
Yes, but it will have less of an impact on the system while it's running.
> INFO: Removed 8368 tuples in 427 pages.
> CPU 0.06s/0.04u sec elapsed 1.54 sec.
> INFO: Pages 24675: Changed 195, Empty 0; Tup 1031519: Vac 8368, Keep 254,
> UnUsed 1739. Total CPU 2.92s/2.58u sec elapsed 65.35 sec.
>
> INFO: Removed 232 tuples in 108 pages.
> CPU 0.01s/0.02u sec elapsed 0.27 sec.
> INFO: Pages 74836: Changed 157, Empty 0; Tup 4716475: Vac 232, Keep 11,
> UnUsed 641.
> Total CPU 10.19s/6.03u sec elapsed 261.44 sec.
What sort of disk array do you have? That seems like a lot of time
considering how little work VACUUM is doing.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, nagler@bivio.biz
Subject: Re: vacuum locking
In-Reply-To: <200310170936.25997.josh@agliodbs.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