Skip site navigation (1) Skip section navigation (2)

Re: --pls reply ASAP

From: Richard Huxton <dev(at)archonet(dot)com>
To: "Chethana, Rao (IE10)" <Chethana(dot)Rao(at)Honeywell(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: --pls reply ASAP
Date: 2006-02-22 14:22:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Chethana, Rao (IE10) wrote:
> Hello!
> Thank you for responding quickly.  I really need ur help.

Please make sure you cc: the list - I don't read this inbox regularly.

> Sir, here r the answers for ur questions, please do tell me what to do
> next(regarding increasing performance of postgresql),  so that I can
> proceed  further.
> How are you using PostgreSQL?
> We r using 7.4.3 with max of (512*6) around 3000 records.

Max of what are (512*6)? Rows? Tables? Sorry - I don't understand what 
you mean here.

Oh, and upgrade to the latest release of 7.4.x - there are important 

> How many concurrent users?
> It configures for 100, but we r using 4 or 5 only.
> Mostly updates or small selects or large summary reports?
> Update,delete,insert operations.
> What hardware do you have?
> X86 based, 233 MHz, 256 MB RAM.

Hmm - not blazing fast, but it'll certainly run on that.

> What configuration changes have you made?
> No changes, we've used default settings.

That will need changing. As Gourish suggested in another reply, read the 
notes here:

You'll want to be careful with the memory settings given that you've 
only got 256MB to play with. Don't allocate too much to PostgreSQL 
itself, let the o.s. cache some files for you.

> Are you having problems with all queries or only some?
> Only some queries, particularly foreign key.

Are you happy that there are indexes on the referring side of the 
foreign key where necessary? The primary keys you reference will have 
indexes on them, the other side will not unless you add them yourself.

> Have you checked the plans for these with EXPLAIN ANALYSE?
> No.

That would be something worth doing then. Find a bad query, run EXPLAIN 
ANALYSE SELECT ... and post a new question with the output and details 
of the tables involved.

> Have you made sure your tables are vacuumed and analysed?
> Yes.

Good. With the limited amount of RAM you have, you'll want to use it as 
efficiently as possible.

   Richard Huxton
   Archonet Ltd


pgsql-performance by date

Next:From: Tom LaneDate: 2006-02-22 15:04:05
Subject: Re: Help with nested loop left join performance
Previous:From: Gourish SingbalDate: 2006-02-22 10:51:20
Subject: Re:

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group