From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "Henrik Cednert (Filmlance)" <henrik(dot)cednert(at)filmlance(dot)se>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade |
Date: | 2017-11-21 18:46:09 |
Message-ID: | 14231.1511289969@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Nov 21, 2017 at 12:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Can you get a profile of where the machine is spending its time during the
>> dump run? On Linux I'd recommend "perf", but on macOS, hmm ...
>> You could use Activity Monitor, but as far as I can see that just captures
>> short-duration snapshots, which might not be representative of a 10-hour
>> run. XCode's Instruments feature would probably be better about giving
>> a full picture, but it has a steep learning curve.
> macOS's "sample" is pretty easy to use and produces text format output
> that is easy to email.
Ah, good idea. But note that only traces one process, so you'd need to
first determine whether it's pg_dump or the backend that's eating most
of the CPU. Or sample both of them.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Henrik Cednert (Filmlance) | 2017-11-21 18:53:29 | Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade |
Previous Message | Robert Haas | 2017-11-21 18:39:26 | Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade |