pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Damien Dougan <damien.dougan@mobilecohesion.com>
To: pgsql-performance@postgresql.org
Subject: Re: Index Performance Help
Date: Thu, 5 Feb 2004 15:54:27 +0000
Message-ID: <200402051554.27672.dev@archonet.com> (raw)
In-Reply-To: <004b01c3ebe1$7e0c9a70$7701a8c0@pestilence>
References: <004b01c3ebe1$7e0c9a70$7701a8c0@pestilence>

On Thursday 05 February 2004 12:13, Damien Dougan wrote:
> Hi All,
>
> I've been seeing very slow read performance on a database of 1 million
> indexed subscribers, which I believe is nothing to do with the data
> itself, but delays on processing the index.
>
> If I make a random jump into the index (say X), it can take about 50ms
> to read the subscriber. If I then make a "close by" lookup (say X+10),
> it takes only about 0.5ms to read the subscriber. Making another lookup
> to a "far away" (say X+1000), it again takes about 50ms to read.

The first time, it has to fetch a block from disk. The second time that disk 
block is already in RAM so it's much faster. The third time it needs a 
different disk block.

> Am I correct in my analysis? Is there anything I can do to improve the
> performance of the index lookups?

Make sure you have enough RAM to buffer your disks. Buy faster disks.

> I've tried increasing the index memory and making a number of queries
> around the index range, but a stray of several hundred indexes from a
> cached entry always results in a major lookup delay.

Yep, that'll be your disks.

> I've also increased the shared memory available to Postgres to 80MB
> incase this is a paging of the index, but it hasn't seemed to have any
> effect.

Probably the wrong thing to do (although you don't mention what hardware 
you've got). Read the tuning document at:
http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php

> Sample analyze output for an initial query:
>
> hydradb=# explain analyze select * from pvsubscriber where actorid =
> 'b3432-asdas-232-Subscriber793500';
...
>                      ->  Index Scan using mc_actor_key on mc_actor
> (cost=0.00..4.08 rows=1 width=69) (actual time=39.497..39.499 rows=1
> loops=1)
...
>  Total runtime: 49.845 ms

> And the analyze output for a "nearby" subscriber (10 indexes away):
>
> hydradb=# explain analyze select * from pvsubscriber where actorid =
> 'b3432-asdas-232-Subscriber793510';
>
...
>                      ->  Index Scan using mc_actor_key on mc_actor
> (cost=0.00..4.08 rows=1 width=69) (actual time=0.220..0.221 rows=1
> loops=1)
>  Total runtime: 0.428 ms
> (15 rows)

That certainly seems to be the big change - the only way to consistently get 
1ms timings is going to be to make sure all your data is cached. Try the 
tuning guide above and see what difference that makes. If that's no good, 
post again with details of your config settings, hardware, number of clients 
etc...

-- 
  Richard Huxton
  Archonet Ltd



view thread (5+ messages)  latest in thread

Message-ID: <200402051554.27672.dev@archonet.com>
Permalink:  ../200402051554.27672.dev@archonet.com/
Also on:    postgresql.org/message-id/200402051554.27672.dev@archonet.com

 · 

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: dev@archonet.com, damien.dougan@mobilecohesion.com
  Subject: Re: Index Performance Help
  In-Reply-To: <200402051554.27672.dev@archonet.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