| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | nobody nowhere <devnull(at)mail(dot)ua> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Re[2]: [PERFORM] SMP on a heavy loaded database |
| Date: | 2013-01-04 21:20:17 |
| Message-ID: | CAGTBQpb8=RcMC5x6tH8aF5eJ53Y+=UX_x2=ksgQskWjitDzSvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Jan 4, 2013 at 6:07 PM, nobody nowhere <devnull(at)mail(dot)ua> wrote:
> 9092 postgres 16 0 4326m 41m 34m S 0.0 0.3 0:00.27 14 postgres: user user_db [local] idle
> 9098 postgres 16 0 4329m 203m 194m S 3.5 1.3 0:00.65 14 postgres: user user_db [local] idle
> 9099 postgres 16 0 4327m 45m 38m S 0.0 0.3 0:00.41 14 postgres: user user_db [local] idle
That looks like pg has been pinned to CPU14. I don't think it's pg's
doing. All I can think of is: check scheduler tweaks, numa, and pg's
initscript. Just in case it's being pinned explicitly.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Westermann | 2013-01-04 21:29:57 | Re: FW: performance issue with a 2.5gb joinded table |
| Previous Message | nobody nowhere | 2013-01-04 21:07:50 | Re[4]: [PERFORM] Re[2]: [PERFORM] SMP on a heavy loaded database |