pg_dump/pg_restore --jobs practical limit?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: pg_dump/pg_restore --jobs practical limit?
Date: 2023-11-01 18:09:10
Message-ID: cabaebac-ae7b-493a-a127-aee941f5f335@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


I will "soon" migrate some 1+ TB database from Pg 9.6.24 on RHEL 6 VMs to Pg
14.latest on RHEL 8 VMs.  The VMs have 10Gbps "NICs", SAN-based LUNs managed
by LVM, and are all on ESX blades.  nproc count on some is 16 and on others
is 32.

Does anyone have experience as to the point of diminishing returns?

IOW, can I crank them processes up to --jobs=30, will I see no gain -- or
even degradation -- after, for example, --jobs=24?

This would be for both pg_dump and pg_restore (which would be run on the
RHEL 8 VM).

--
Born in Arizona, moved to Babylonia.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mateusz Henicz 2023-11-01 18:16:00 Re: missing client_hostname
Previous Message Atul Kumar 2023-11-01 18:02:41 Re: missing client_hostname