| From: | Bryan White <nicktook(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_restore error |
| Date: | 2010-04-17 22:09:24 |
| Message-ID: | l2w649cb4eb1004171509p1c20174eg9940313652c2bd07@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Apr 17, 2010 at 5:53 PM, Steve Crawford
<scrawford(at)pinpointresearch(dot)com> wrote:
> Bryan White wrote:
>>
>> ...
>> The new server is a dual socket Nahalem. 8 cores, 16 threads, 48 GB
>> ram, 2 WAL drives in RAID1 and 12 database drives in RAID10.
>>
>
> I would try setting -j higher - in your case try 8 for starters. Also turn
> off fsync and autovacuum (and turn them back on !!!). See these and more
> tips at:
> http://it.toolbox.com/blogs/database-soup/using-84-parallel-restore-with-your-83-or-82-database-31575
>
Success. The -j6 run completed. The time to restore went from 152
minutes to 45 minutes. I was already doing some of the things on the
above page. I plan on implementing others and than do a few test runs
to find the optimal number of jobs.
Thanks!
--
Bryan White
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samuel Stearns | 2010-04-18 03:21:18 | Re: FW: More than 1 pg_database Entry for Database - Thread #2 |
| Previous Message | Steve Crawford | 2010-04-17 21:53:36 | Re: pg_restore error |