Full Version: 32-bit or 64-bit
How many are running a 64-bit os in their servers now?
32-bit for me. Still a little chicken to swap over to 64-bit using 32-bit applications.
I have an internal 64-bit server and it works fine but I don't use it for testing; yet.
I have an internal 64-bit server and it works fine but I don't use it for testing; yet.
Home, 64-Bit, Server 32-Bit. Why have it using extra resources than it needs? It's not like you will SEE what's it's doing. 64-Bits to me is moreso for graphics purposes in which I do animation and movie editing.
Uhh, what? That is absurd.
Unlike Home software, most of which is optimized for 32-Bit processing, thus wasting 32-bits of power, Server software *is* optimized for 64-Bit processing, and where it drops back to 32-Bit you end up with a dual op per cycle instead of being restricted to half the bus like you are with the average Home OS.
It is more wasteful to have a 64-bit CPU sitting in a server using half its power than to go ahead and take advantage of it using a 64-bit OS and its associated packages. The throughput it *is* faster, and you *do* see a difference, which is more than can be said about the majority of "Home" systems.
Unlike Home software, most of which is optimized for 32-Bit processing, thus wasting 32-bits of power, Server software *is* optimized for 64-Bit processing, and where it drops back to 32-Bit you end up with a dual op per cycle instead of being restricted to half the bus like you are with the average Home OS.
It is more wasteful to have a 64-bit CPU sitting in a server using half its power than to go ahead and take advantage of it using a 64-bit OS and its associated packages. The throughput it *is* faster, and you *do* see a difference, which is more than can be said about the majority of "Home" systems.
I should stop feeding the trolls.
On one hand it seems like a shame to still be running 64 bit cpus with 32 bit code, since the cpus have been 64 bit forever now. It seems the control panel glitches are finally a thing of the past with 64-bit.
On the other hand, I read that common lamp server application memory usage can actually be 40% greater on a 64-bit os, so that doesn't seem so good... i.e. with 8 GB on a 64-bit os it might be like having 4.8 GB on a 32-bit os which isn't so exciting (if budget limited from taking a real leap in RAM magnitude)
On the other hand, I read that common lamp server application memory usage can actually be 40% greater on a 64-bit os, so that doesn't seem so good... i.e. with 8 GB on a 64-bit os it might be like having 4.8 GB on a 32-bit os which isn't so exciting (if budget limited from taking a real leap in RAM magnitude)
My VPS @ work
Gentoo Box @ Home
Vista Box @ Home
QUOTE
[tdurden@c2111-tdurden ~]$ uname -a && cat /proc/cpuinfo
Linux c2111-tdurden 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 CST 2007 i686 i686 i386 GNU/Linux
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel® Xeon™ CPU 2.80GHz
stepping : 8
cpu MHz : 2792.096
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss nx constant_tsc up pni ds_cpl
bogomips : 5663.38
Linux c2111-tdurden 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 CST 2007 i686 i686 i386 GNU/Linux
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel® Xeon™ CPU 2.80GHz
stepping : 8
cpu MHz : 2792.096
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss nx constant_tsc up pni ds_cpl
bogomips : 5663.38
Gentoo Box @ Home
QUOTE
transistor ~ # uname -a && cat /proc/cpuinfo
Linux transistor 2.6.24-gentoo-r8 #3 SMP Sat Jun 7 16:52:08 Fri Jan 26 14:15:21 CST 2007 i686 AMD Athlon™ 64 Processor 3000+ AuthenticAMD GNU/Linux
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 12
model name : AMD Athlon™ 64 Processor 3000+
stepping : 0
cpu MHz : 2000.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up ts fid vid ttp
bogomips : 4021.16
clflush size : 64
Linux transistor 2.6.24-gentoo-r8 #3 SMP Sat Jun 7 16:52:08 Fri Jan 26 14:15:21 CST 2007 i686 AMD Athlon™ 64 Processor 3000+ AuthenticAMD GNU/Linux
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 12
model name : AMD Athlon™ 64 Processor 3000+
stepping : 0
cpu MHz : 2000.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up ts fid vid ttp
bogomips : 4021.16
clflush size : 64
Vista Box @ Home
QUOTE
System
--------------------------------------------------------------------------------
Manufacturer System manufacturer
Model System Product Name
Total amount of system memory 6.00 GB RAM
System type 64-bit operating system
Number of processor cores 2
--------------------------------------------------------------------------------
Manufacturer System manufacturer
Model System Product Name
Total amount of system memory 6.00 GB RAM
System type 64-bit operating system
Number of processor cores 2
64's for hosting, 32's at the office and home.
*nod* Markccausa.
Back on the memory thing, since I didn't reply before ... I can't figure out where people read this stuff ... Reporters who don't understand anything, or what ...
Memory-wise, okay --- you've got a 64-bit chunk of data. It's gonna take up 64-bits instead of 32-bits. Duh. You've got a 32-bit chunk of data. It's gonna take up 32-bits, only, now there are two spaces for that 32-bit data when you're running 64-bit.
My God ... Try thinking, "I'm gonna put drain two pipes on my tub, but it's gonna drain at the same speed because they're the same size." Wouldn't make any sense, would it?
Back on the memory thing, since I didn't reply before ... I can't figure out where people read this stuff ... Reporters who don't understand anything, or what ...
Memory-wise, okay --- you've got a 64-bit chunk of data. It's gonna take up 64-bits instead of 32-bits. Duh. You've got a 32-bit chunk of data. It's gonna take up 32-bits, only, now there are two spaces for that 32-bit data when you're running 64-bit.
My God ... Try thinking, "I'm gonna put drain two pipes on my tub, but it's gonna drain at the same speed because they're the same size." Wouldn't make any sense, would it?
QUOTE (Catalyst @ Mar 17 2009, 02:03 AM) 
*nod* Markccausa.
Back on the memory thing, since I didn't reply before ... I can't figure out where people read this stuff ... Reporters who don't understand anything, or what ...
Memory-wise, okay --- you've got a 64-bit chunk of data. It's gonna take up 64-bits instead of 32-bits. Duh. You've got a 32-bit chunk of data. It's gonna take up 32-bits, only, now there are two spaces for that 32-bit data when you're running 64-bit.
My God ... Try thinking, "I'm gonna put drain two pipes on my tub, but it's gonna drain at the same speed because they're the same size." Wouldn't make any sense, would it?
Back on the memory thing, since I didn't reply before ... I can't figure out where people read this stuff ... Reporters who don't understand anything, or what ...
Memory-wise, okay --- you've got a 64-bit chunk of data. It's gonna take up 64-bits instead of 32-bits. Duh. You've got a 32-bit chunk of data. It's gonna take up 32-bits, only, now there are two spaces for that 32-bit data when you're running 64-bit.
My God ... Try thinking, "I'm gonna put drain two pipes on my tub, but it's gonna drain at the same speed because they're the same size." Wouldn't make any sense, would it?
64BIT
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.