pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: Litao Wu <litaowu@yahoo.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: vacuum_mem
Date: Thu, 08 Jul 2004 14:25:30 -0400
Message-ID: <1089311129.5999.219.camel@jester> (raw)
In-Reply-To: <20040708180343.88032.qmail@web13121.mail.yahoo.com>
References: <20040708180343.88032.qmail@web13121.mail.yahoo.com>

> It seems vacuum_mem does not have performance 
> effect at all.

Wrong conclusion. It implies that your test case takes less than 64M of
memory to track your removed tuples. I think it takes 8 bytes to track a
tuple for vacuuming an index, which means it should be able to track
800000 deletions. Since you're demonstration had 750000 for removal,
it's under the limit.

Try your test again with 32MB; it should make a single sequential pass
on the table, and 2 passes on each index for that table.

Either that, or do a few more aborted updates.





view thread (2+ messages)

Message-ID: <1089311129.5999.219.camel@jester>
Permalink:  ../1089311129.5999.219.camel@jester/
Also on:    postgresql.org/message-id/1089311129.5999.219.camel@jester

 · 

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-performance@postgresql.org
  Cc: pg@rbt.ca, litaowu@yahoo.com
  Subject: Re: vacuum_mem
  In-Reply-To: <1089311129.5999.219.camel@jester>

* 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