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

Re: %100 CPU on Windows Server 2003

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Allen Sooredoo <Allen_Sooredoo(at)carrefour(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, Mehmet Demir <Mehmet_Demir(at)carrefour(dot)com>
Subject: Re: %100 CPU on Windows Server 2003
Date: 2011-04-25 23:44:05
Message-ID: BANLkTik2z8XZoS74WBDa2pNPZh31yJFetQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Wed, Apr 20, 2011 at 10:55 AM, Allen Sooredoo <
Allen_Sooredoo(at)carrefour(dot)com> wrote:

> Hi,
> we are facing a performance issue on Postgres 8.4, the CPU reaches 100%
> with less than 50 simultaneous users.
>
> We were thinking to migrate the HR system from Oracle to Postgres but now
> that we have those big performance problems on relatively small
> applications, we are questioning this choice.
>
> The machine configuration, dedicated to Postgres is as follow:
> RAM: 3GB
> CPU: Intel Xeon CPU 3.2 Ghz
>
> Could you please provide us some support regarding this issue?
>

Probably, but you'll need to provide more details.  It is likely that you
have some queries that need to be tuned, and possibly some settings that
need to be changed.  But without some information about what is using up all
the CPU time, it's hard to speculate as to what the problem might be.

http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

You might also want to read this article:

http://www.linux.com/learn/tutorials/394523-configuring-postgresql-for-pretty-good-performance

I've also found that log_min_duration_statement is pretty useful for
figuring out where the CPU time is going - it helps you find your
long-running queries.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-performance by date

Next:From: Robert HaasDate: 2011-04-25 23:54:34
Subject: Re: Slow deleting tables with foreign keys
Previous:From: J SissonDate: 2011-04-25 19:30:59
Subject: Time to put theory to the test?

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