pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Steve Crawford <scrawford@pinpointresearch.com>
To: Craig James <craig_james@emolecules.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Occasional giant spikes in CPU load
Date: Wed, 07 Apr 2010 16:14:01 -0700
Message-ID: <4BBD11B9.3040707@pinpointresearch.com> (raw)
In-Reply-To: <4BBD1033.9080905@emolecules.com>
References: <k2pda0294261004061437p9cd3810dqe9ce528b6ddb0873@mail.gmail.com>
	<m2m603c8f071004071413w1f2d2497hbbe07d9c6491848f@mail.gmail.com>
	<4BBCFB12.1010306@emolecules.com>
	<8127.1270677548@sss.pgh.pa.us>
	<4BBD1033.9080905@emolecules.com>


>> ...Can you
>> correlate the spikes with anything like that?
>
> Not that I know of.  Just regular web traffic.  On the backup server 
> these events happen occasionally even when there is little or no web 
> traffic, and nobody logged in doing maintenance.
What, if anything, are you logging in the PostgreSQL logs? Anything 
interesting, there?

Cheers,
Steve

view thread (31+ messages)  latest in thread

Message-ID: <4BBD11B9.3040707@pinpointresearch.com>
Permalink:  ../4BBD11B9.3040707@pinpointresearch.com/
Also on:    postgresql.org/message-id/4BBD11B9.3040707@pinpointresearch.com

copy link · copy postgr.es

reply

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: scrawford@pinpointresearch.com, craig_james@emolecules.com, tgl@sss.pgh.pa.us
  Subject: Re: Occasional giant spikes in CPU load
  In-Reply-To: <4BBD11B9.3040707@pinpointresearch.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