Re: [HACKERS] A Better External Sort?

From: "Luke Lonergan" <LLonergan(at)greenplum(dot)com>
To: "Michael Stone" <mstone+postgres(at)mathom(dot)us>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: [HACKERS] A Better External Sort?
Date: 2005-10-05 15:24:07
Message-ID: 3E37B936B592014B978C4415F90D662DE11B55@MI8NYCMAIL06.Mi8.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Nope - it would be disk wait.

COPY is CPU bound on I/O subsystems faster that 50 MB/s on COPY (in) and about 15 MB/s (out).

- Luke

-----Original Message-----
From: Michael Stone [mailto:mstone+postgres(at)mathom(dot)us]
Sent: Wed Oct 05 09:58:41 2005
To: Martijn van Oosterhout
Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-performance(at)postgresql(dot)org
Subject: Re: [HACKERS] [PERFORM] A Better External Sort?

On Sat, Oct 01, 2005 at 06:19:41PM +0200, Martijn van Oosterhout wrote:
>COPY TO /dev/null WITH binary
>13MB/s 55% user 45% system (ergo, CPU bound)
[snip]
>the most expensive. But it does point out that the whole process is
>probably CPU bound more than anything else.

Note that 45% of that cpu usage is system--which is where IO overhead
would end up being counted. Until you profile where you system time is
going it's premature to say it isn't an IO problem.

Mike Stone

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-10-05 15:26:27 Re: Interesting optimizer's supposition in 8.1
Previous Message Gaetano Mendola 2005-10-05 15:20:30 wrong optimization ( postgres 8.0.3 )

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Stone 2005-10-05 15:33:49 Re: [HACKERS] A Better External Sort?
Previous Message Frank Wiles 2005-10-05 15:05:43 Re: Is There Any Way ....