From: | "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | database tuning |
Date: | 2002-08-15 00:03:47 |
Message-ID: | 73309C2FDD95D11192E60008C7B1D5BB04C73E16@snt452.corp.bcbsm.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Howdy:
I'm running PostgreSQL 7.2.1 on Redhat Linux 7.2
kernel 2.4.7-10.
I have a question about performance tuning
with PostgreSQL.
A few weeks ago, I installed and migrated data
from version 7.1.3 to version 7.2.1. After that,
it seems that when I load data, have users do
a select / insert / or otherwise access the
database, it takes a very long time to complete.
When looking at the processes with 'top', what
used to happen was whatever was running would take
all of the resources (or, whatever was available);
so, if there were say, four 'selects' from the
database, there would be four processes fighting
for CPU time. Now it seems that the processes
are more idle and are not using the CPU as effectively
and efficiently as they could.
How can I change this? What can I do to tune
the database more efficiently?
Thanks!
-X
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Mock | 2002-08-15 00:17:10 | Re: performance with triggers depends on table size? |
Previous Message | Orr, Steve | 2002-08-14 22:33:13 | Migrating MySQL data to PostgreSQL |