Re: 8.3 / 8.2.6 restore comparison - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: 8.3 / 8.2.6 restore comparison
Date
Msg-id 47C05D8F.1000104@kaltenbrunner.cc
Whole thread Raw
In response to Re: 8.3 / 8.2.6 restore comparison  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.3 / 8.2.6 restore comparison  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: 8.3 / 8.2.6 restore comparison  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> Yeah, that... is beyond my abilities. Well reading it is anyway. I can
>> provide any information people want though. Tom? Greg? Andrew? Somebody?
>> What information do you want from me to help you track this down?
> 
> The vmstat output you showed before said user CPU time was only around
> 12%, which seems to destroy Luke's thesis that data conversion time
> is the problem.  IIRC we were speculating that data was being written
> in a pattern that required a lot of seeking thus ruining throughput,
> but we didn't have any hard evidence of that.  Did you do the strace'ing
> I suggested?


Joshua said this is an 8 core box - so 12% would about equal to one core 
being maxed out completely CPU wise which seems to correlate fairly well 
with my experience (COPY being CPU bottlenecked on fast hardware without 
any real culprit to find in profiles).



Stefan


pgsql-hackers by date:

Previous
From: Mathias Hasselmann
Date:
Subject: Re: [PATCHES] Avahi support for Postgresql
Next
From: "Joshua D. Drake"
Date:
Subject: Re: 8.3 / 8.2.6 restore comparison