multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 26 Feb 2008 07:43:23 -0800
"Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:

> On Mon, 25 Feb 2008 22:25:09 -0800
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
>
> 24 connections: 3.5 hours
> 12 connections: 4.5 hours
>

24 connections RAW_BUF_SIZE 524288 3.5 hours

However one observation that I am going to (try) to test is that we are
spending a lot of time waiting for the last thread to finish. I
wouldn't be surprised if I could cut the time in half if I could script
this out to do:

table.data->table.pk->table.index
table.data->table.pk->table.index
table.data->table.pk->table.index
table.data->table.pk->table.index
constraints

versus

table.data
table.data
table.data
table.pk
table.pk
table.pk
table.index

...

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHxJ3+ATb/zqfZUUQRAlURAKCtOSbHoWTNSkzV0U48Ib0P/8SSNgCdFeWK
v6Q1l5BBGxqqtPu1UMhA81E=
=VA2+
-----END PGP SIGNATURE-----