| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Petrilli <petrilli(at)gmail(dot)com> |
| Cc: | PFC <lists(at)boutiquenumerique(dot)com>, Vivek Khera <vivek(at)khera(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Impact of checkpoint_segments under continual load conditions |
| Date: | 2005-07-19 17:05:25 |
| Message-ID: | 7436.1121792725@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Christopher Petrilli <petrilli(at)gmail(dot)com> writes:
> As I'm doing this, I'm noticing something *VERY* disturbing to me:
> postmaster backend: 20.3% CPU
> psql frontend: 61.2% CPU
> WTF? The only thing going through the front end is the COPY command,
> and it's sent to the backend to read from a file?
Are you sure the backend is reading directly from the file, and not
through psql? (\copy, or COPY FROM STDIN, would go through psql.)
But even so that seems awfully high, considering how little work psql
has to do compared to the backend. Has anyone ever profiled psql doing
this sort of thing? I know I've spent all my time looking at the
backend ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Petrilli | 2005-07-19 17:13:05 | Re: Impact of checkpoint_segments under continual load conditions |
| Previous Message | Christopher Petrilli | 2005-07-19 16:54:35 | Re: Impact of checkpoint_segments under continual load conditions |