From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Jasen Lentz <jlentz(at)sescollc(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_basebackup inconsistent performance |
Date: | 2020-05-06 16:29:45 |
Message-ID: | 20200506162945.GT13712@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Jasen Lentz (jlentz(at)sescollc(dot)com) wrote:
> Where are the machines you are backing up from/to relative to each on the network?
> Direct ethernet connection between 10G network interfaces
Is the backup server shared among other systems..?
> Is there increased activity on the database servers e.g. inserts, updates, etc during the extended backups?
> Not according to sar reports
And there's no increased activity on the backup server either?
Have you looked at network traffic for the duration? And/or disk i/o on
each system? If you ran a backup once and then immediately after and
that's the 'fast' case then you may be seeing performance be better due
to a lot of data being in the filesystem cache. pg_basebackup being
single-threaded probably doesn't help here either, you might want to
consider one of the parallel-backup options.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-05-06 16:30:07 | Re: White space affecting parsing of range values |
Previous Message | Thom Brown | 2020-05-06 16:19:51 | Re: White space affecting parsing of range values |