From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | Naveen Palavalli <palavall(at)ISI(dot)EDU> |
Cc: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Query on Postgresql performance |
Date: | 2003-09-04 02:01:10 |
Message-ID: | 1062640870.14624.13.camel@tokyo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, 2003-09-03 at 15:32, Naveen Palavalli wrote:
> shared_buffers = 200
If you're using a relatively modern machine, this is probably on the low
side.
> 1) Effects related to Vaccum :- I performed 10 trials of adding and
> deleting entries . In each trial , 1 client adds 10,000 entries and
> then deletes them . During the course of these 10 trials , the Add
> Rates (rate at which my server can add entries to the Postgresql
> database ) drops from around 200 Adds/second in the 1st trial to
> around 100 Adds/second in the 10th trial . But when I do a Vaccuum ,
> Immediately I get back the Add Rates to around 200 Adds/Second .
Well, there's nothing wrong with vacuuming frequently (since it won't
block concurrent database operations, and the more often you vacuum, the
less time each vacuum takes).
> I was using Postgresql 7.3.3 earlier but it kept crashing the database
> after a Vaccum . So I switched to a older and stabler version 7.2.4
Can you reproduce the 7.3.3 crash? (BTW, in the future, it would be
appreciated if you could report these kinds of bugs to the dev team).
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Federico Sevilla III | 2003-09-04 03:04:04 | PostgreSQL Reliability when fsync = false on Linux-XFS |
Previous Message | Neil Conway | 2003-09-04 01:54:37 | Re: SELECT's take a long time compared to other DBMS |