From: Dave Cramer <pg@fastcrypt.com>
To: Ben Bostow <ben@viatornetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Problems with high traffic
Date: Thu, 06 Jan 2005 08:06:51 -0500
Message-ID: <41DD37EB.8050206@fastcrypt.com> (raw)
In-Reply-To: <5BE6686A-5FB9-11D9-9915-000D93C56ABE@viatornetworks.com>
References: <5BE6686A-5FB9-11D9-9915-000D93C56ABE@viatornetworks.com>
Ben
Well, we need more information
pg version, hardware, memory, etc
you may want to turn on log_duration to see exactly which statement is
causeing the problem. I'm assuming since it is taking a lot of CPU it
will take some time to complete( this may not be true)
On your last point, that is where you will get the most optimization,
but I'd still use log_duration to make sure optimizing the statement
will actually help.
dave
Ben Bostow wrote:
> I'm still relatively new to Postgres. I usually just do SQL
> programming but have found my self having to administer the DB now. I
> have I have a problem on my website that when there is high amounts of
> traffic coming from one computer to my web server. I suspect it is
> because of a virus. But what when I notice this, my processor drops to
> 0.0% idle with postmaster being my highest CPU user. Under normal
> circumstances the processor runs >90% idle or <10% used. I have tried
> tuning postgres but it doesn't seem to make a difference, unless I am
> doing something wrong. If I would like to find a solution other than
> rewriting all of my SQL statements and creating them to take the least
> amount of time to process.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561
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: pg@fastcrypt.com, ben@viatornetworks.com
Subject: Re: Problems with high traffic
In-Reply-To: <41DD37EB.8050206@fastcrypt.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