pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Davis <pgsql@j-davis.com>
To: sthomas@optionshouse.com
Cc: Mark Thornton <mthornton@optrak.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance of CLUSTER
Date: Mon, 11 Jun 2012 16:53:57 -0700
Message-ID: <1339458837.12042.9.camel@sussancws0025> (raw)
In-Reply-To: <4FD5F5DC.3080507@optionshouse.com>
References: <4FD458CA.3070902@optrak.com>
	<4FD5F5DC.3080507@optionshouse.com>

On Mon, 2012-06-11 at 08:42 -0500, Shaun Thomas wrote:
> On 06/10/2012 03:20 AM, Mark Thornton wrote:
> 
> > 4. 3980922 rows, 1167MB, 276s
> > 5. 31843368 rows, 9709MB, ~ 10 hours
> 
> Just judging based on the difference between these two, it would appear 
> to be from a lot of temp space thrashing. An order of magnitude more 
> rows shouldn't take over 100x longer to cluster, even with GIST. What's 
> your maintenance_work_mem setting?

GiST can have a large impact depending on all kinds of factors,
including data distribution.

9.2 contains some important improvements in GiST build times for cases
where the index doesn't fit in memory. Mark, can you please try your
experiments on the 9.2beta and tell us whether that helps you?

Regards,
	Jeff Davis




view thread (6+ messages)

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

 · 

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: pgsql@j-davis.com, sthomas@optionshouse.com, mthornton@optrak.com
  Subject: Re: Performance of CLUSTER
  In-Reply-To: <1339458837.12042.9.camel@sussancws0025>

* 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