From: | Craig James <craig_james(at)emolecules(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Occasional giant spikes in CPU load |
Date: | 2010-06-25 13:48:43 |
Message-ID: | 4C24B3BB.3070901@emolecules.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 6/24/10 9:04 PM, Tom Lane wrote:
> Craig James<craig_james(at)emolecules(dot)com> writes:
>> So what is it that will cause every single Postgres backend to come to life at the same moment, when there's no real load on the server? Maybe if a backend crashes? Some other problem?
>
> sinval queue overflow comes to mind ... although that really shouldn't
> happen if there's "no real load" on the server. What PG version is
> this?
8.3.10. Upgraded based on your advice when I first asked this question.
> Also, the pg_stat_activity view contents when this happens would
> probably be more useful to look at than "top" output.
I'll try. It's hard to discover anything because the whole machine is overwhelmed when this happens. The only way I got the top(1) output was by running it high priority as root using nice(1). I can't do that with a Postgres backend, but I'll see what I can do.
Craig
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2010-06-25 14:14:48 | Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.) |
Previous Message | Yeb Havinga | 2010-06-25 11:28:57 | Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.) |