From: | "Shea,Dan [CIS]" <Dan(dot)Shea(at)ec(dot)gc(dot)ca> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Cluster and vacuum performance |
Date: | 2004-03-09 20:17:59 |
Message-ID: | F2D63B916C88C14D9B59F93C2A5DD33F0B919E@cisxa.cis.ec.gc.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I have a few questions about cluster and vacuum.
We have a table that is 56 GB in size and after a purge based on dates 16GB
was made available as reported below.
PWFPM_DEV=# vacuum full verbose analyze forecastelement;
INFO: vacuuming "public.forecastelement"
INFO: "forecastelement": found 93351479 removable, 219177133 nonremovable
row versions in 6621806 pages
DETAIL: 0 dead row versions cannot be removed yet.
Nonremovable row versions range from 156 to 192 bytes long.
There were 611201 unused item pointers.
Total free space (including removable row versions) is 16296891960 bytes.
1974172 pages are or will become empty, including 26 at the end of the
table.
1990268 pages containing 15794855436 free bytes are potential move
destinations.
CPU 467.29s/48.52u sec elapsed 4121.69 sec.
How can you improve the performance of cluster?
1. BY increasing sort_mem?
2. Does increasing vacuum_mem help?
3. Does checkpoint_segments improve it?
Dan
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2004-03-09 20:26:55 | Re: [HACKERS] WAL Optimisation - configuration and usage |
Previous Message | Joe Conway | 2004-03-09 18:48:33 | Re: [OT] Respository [was Re: [PERFORM] Feature request: |