What hard drives are you running? IDE / SCSI / SATA? Are they in a hardware
/ software RAID? PG still has to commit changes to disk regardless of
swapping - there might be a bottleneck at the disk I/O for the commits.
Also, your postmaster doesn't seem to be using much RAM. Have you tweaked
the conf files to allow the pg processes to use more RAM than default?
Cheers,
~p
-----Original Message-----
From: pgsql-novice-owner@postgresql.org
[mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Neil Aggarwal
Sent: Wednesday, 28 February 2007 13:50
To: pgsql-novice@postgresql.org
Subject: [NOVICE] Crappy performance even though not swapping
Hello:
I have a Java program that is trying to import over 8 million
rows from a text file.
When the program starts up, it runs fine, but after a while
it begins to crawl.
This is usually symptomatic of a machine that started swapping,
but take a look at the attached output from top.
I am using a LOT of memory, but the swap is still very
low. I don't think the machine should be paging to disk.
The CPU states show that the cpus are spending most of their time
in an idle state. The process list shows the postmaster and java
processes are less than 10 percent the CPU cycles.
Having said that, the load average is still about 2.
Any ideas what could be going on?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.
Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
