| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: cpu bound postgresql setup. |
| Date: | 2010-06-24 18:58:23 |
| Message-ID: | 1277405847-sup-5188@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Excerpts from Rajesh Kumar Mallah's message of jue jun 24 13:25:32 -0400 2010:
> What prompted me to post to list is that the server transitioned from
> being IO bound to CPU bound and 90% of syscalls being
> lseek(XXX, 0, SEEK_END) = YYYYYYY
It could be useful to find out what file is being seeked. Correlate the
XXX with files in /proc/<pid>/fd (at least on Linux) to find out more.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-06-24 19:00:27 | Re: cpu bound postgresql setup. |
| Previous Message | Josh Berkus | 2010-06-24 18:56:44 | Re: PostgreSQL as a local in-memory cache |