From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org, grupos(at)carvalhaes(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [PERFORM] pg_restore taking 4 hours! |
Date: | 2004-12-01 20:19:00 |
Message-ID: | 200412011219.00248.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
Rodrigo,
> Our machine it's a Dell Server Power Edge 1600sc (Xeon 2,4Ghz, with 1GB
> memory, 7200 RPM disk). I don't think that there is a machine problem
> because it's a server dedicated for the database and the cpu utilization
> during the restore is around 30%.
In addition to Tom and Shridhar's advice, a single IDE disk is simply going to
make restores slow. A 500MB data file copy on that disk, straight, would
take up to 15 min. If this is for your ISV application, you need to
seriously re-think your hardware strategy; spending less on processors and
more on disks would be wise.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-01 20:22:45 | Re: createlang plperl fails with 8.0 beta5 |
Previous Message | Joachim Zobel | 2004-12-01 19:40:20 | createlang plperl fails with 8.0 beta5 |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-12-01 20:25:42 | Re: Using "LIMIT" is much faster even though, searching |
Previous Message | Tom Lane | 2004-12-01 20:06:58 | Re: query with timestamp not using index |