Thread: please comment on cpu 32 bit or 64 bit

please comment on cpu 32 bit or 64 bit

From
"wisan watcharinporn"
Date:
please help me ,
comment on postgresql (8.x.x) performance on cpu AMD, INTEL
and why i should use 32 bit or 64 cpu ? (what the performance difference)

thank you

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


Re: please comment on cpu 32 bit or 64 bit

From
Tom Lane
Date:
"wisan watcharinporn" <maccran@hotmail.com> writes:
> comment on postgresql (8.x.x) performance on cpu AMD, INTEL
> and why i should use 32 bit or 64 cpu ? (what the performance difference)

For most database applications, you're better off spending your money
on faster disk drives and/or more RAM than on a sexier CPU.

Maybe your application doesn't follow that general rule --- but since
you told us exactly zero about what your application is, this advice
is worth what you paid for it ...

            regards, tom lane

Re: please comment on cpu 32 bit or 64 bit

From
Chris Browne
Date:
maccran@hotmail.com ("wisan watcharinporn") writes:
> please help me ,
> comment on postgresql (8.x.x) performance on cpu AMD, INTEL
> and why i should use 32 bit or 64 cpu ? (what the performance difference)

Generally speaking, the width of your I/O bus will be more important
to performance than the width of the processor bus.

That is, having more and better disk will have more impact on
performance than getting a better CPU.

That being said, if you plan to have a system with significantly more
than 2GB of memory, there seem to be pretty substantial benefits to
the speed of AMD memory bus access, and that can be quite significant,
given that if you have a lot of memory, and thus are often operating
out of cache, and are slinging around big queries, THAT implies a lot
of shoving data around in memory.  AMD/Opteron has a way faster memory
bus than the Intel/Xeon systems.

But this is only likely to be significant if you're doing processing
intense enough that you commonly have >> 4GB of memory in use.

If not, then you'd better focus on I/O speed, which is typically
pretty independent of the CPU...
--
(format nil "~S@~S" "cbbrowne" "ntlug.org")
http://www.ntlug.org/~cbbrowne/rdbms.html
"Anyway I know how to not be bothered by consing on the fly."
-- Dave Moon