New server ordered


Recommended Posts

does it beat my webbox for animerising.net? 8 cores, 16 GB ram

info :)

processor : 0

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 0

cpu cores : 4

apicid : 0

initial apicid : 0

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3989.76

clflush size : 64

power management:

processor : 1

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 1

siblings : 4

core id : 0

cpu cores : 4

apicid : 4

initial apicid : 4

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.04

clflush size : 64

power management:

processor : 2

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 2

cpu cores : 4

apicid : 2

initial apicid : 2

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.03

clflush size : 64

power management:

processor : 3

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 1

siblings : 4

core id : 2

cpu cores : 4

apicid : 6

initial apicid : 6

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.04

clflush size : 64

power management:

processor : 4

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 1

cpu cores : 4

apicid : 1

initial apicid : 1

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.04

clflush size : 64

power management:

processor : 5

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 1

siblings : 4

core id : 1

cpu cores : 4

apicid : 5

initial apicid : 5

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.05

clflush size : 64

power management:

processor : 6

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 3

cpu cores : 4

apicid : 3

initial apicid : 3

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.03

clflush size : 64

power management:

processor : 7

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel® Xeon® CPU E5405 @ 2.00GHz

stepping : 6

cpu MHz : 1994.883

cache size : 6144 KB

physical id : 1

siblings : 4

core id : 3

cpu cores : 4

apicid : 7

initial apicid : 7

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority

bogomips : 3990.05

clflush size : 64

power management:

For performance I would say no, for file servers and print servers yes virtulise!

Having virtualized everything from file and print servers, IIS and Apache webservers, Microsoft and MySQL servers, Microsoft Exchange, Active Directory domain controllers, Oracle, various application servers, and 250+ virtual desktops... I can say with some authority, you don't take a (significant) performance hit when you virtualize correctly. With a desktop virtualization solution like VMWare Fusion/Workstation or Microsoft Virtual PC, you do, because you don't really have solid hardware access. With a virtualization hypervisor like VMWare ESX or Microsoft Hyper-V, the game is totally different.

Computer hardware, and especially servers, are far more powerful then what any one operating system and application combination can take advantage of. VMWare wouldn't be making money hand over fist if the only thing people were doing with it was virtualizing print servers.

In terms of being a single point of failure, you actually create a more robust infrastructure with virtualization. I used to think the same thing up until a few years ago, but look up ESX vMotion or Hyper-V Live Migration, and see what I'm talking about. It would require a NAS/SAN which isn't in the equation right now I'm sure. If you were virtualized, any hardware failure that required a system to be taken off line would be simply migrating the virtual guests to another host, all with NO network connection loss. It could also handle automatically migrating systems based on resource usage.

Congrats on the new server BTW.

Having virtualized everything from file and print servers, IIS and Apache webservers, Microsoft and MySQL servers, Microsoft Exchange, Active Directory domain controllers, Oracle, various application servers, and 250+ virtual desktops... I can say with some authority, you don't take a (significant) performance hit when you virtualize correctly. With a desktop virtualization solution like VMWare Fusion/Workstation or Microsoft Virtual PC, you do, because you don't really have solid hardware access. With a virtualization hypervisor like VMWare ESX or Microsoft Hyper-V, the game is totally different.

Computer hardware, and especially servers, are far more powerful then what any one operating system and application combination can take advantage of. VMWare wouldn't be making money hand over fist if the only thing people were doing with it was virtualizing print servers.

In terms of being a single point of failure, you actually create a more robust infrastructure with virtualization. I used to think the same thing up until a few years ago, but look up ESX vMotion or Hyper-V Live Migration, and see what I'm talking about. It would require a NAS/SAN which isn't in the equation right now I'm sure. If you were virtualized, any hardware failure that required a system to be taken off line would be simply migrating the virtual guests to another host, all with NO network connection loss. It could also handle automatically migrating systems based on resource usage.

Congrats on the new server BTW.

Exactly, without a NAS/SAN and more servers of a similar size to migrate to should one fail, virtualisation isn't really an option.

  • 2 weeks later...
  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.