Erm. I think you've missed the point slightly.
All that CPU power is so that you can watch movies and play MP3s whilst
waiting for VACUUM to finish. Be sure to have your movie files on
another disk and I/O channel, so that frames don't get lost - but of course ;).
Note: if you really don't need the CPU power, what you could do is
underclock your CPU, that way you can run cooler and more reliably (maybe
even go fanless) or you can get someone else to do it for you and buy a
Hope that helps,
 When you are vacuuming really large databases you might even want to
crack crypto whilst you're at it :). Or do some ray tracing, or
machinima/animated films. Of course with the advances of Postgresql 7.2
these times of repose and reflection will become briefer, rarer and more
precious. How we will miss glimpses of The Boss yelling and hammering on
the locked server room door whilst the vacuum is going on. But take heart,
for the Benevolent Developers in their great wisdom and grace hath provided
VACUUM FULL, and our disk buffers overfloweth with joy.
At 10:52 PM 4/26/02 -0400, postgres(at)vrane(dot)com wrote:
>The moral I get from this benchmark is that AMD is certainly
>not much better preformance/price wise at least not for
>a database server
>In fact for various reasons I am going to go with an intel
>Another gripe I have is that vacuum process does not eat up 100%
>of cpu. In the beginning it peaks around 80% and at the end
>it is stuck around 20%.
>Whenever I have a long running process and
>it is not eating up 100% of cpu I feel I am not getting my money's
>worth for the cpu. I wonder why vacuum process is not more parallelized
>if at all. I can imagine manually vacuuming many tables in parallel
>and it might eat up all cpu and I wonder whether it might finish quicker.
In response to
pgsql-general by date
|Next:||From: Mathieu Arnold||Date: 2002-04-27 10:10:11|
|Subject: Re: delete column|
|Previous:||From: Hegyvari Krisztian||Date: 2002-04-27 09:16:08|
|Subject: creating a dump|