Joseph Marton wrote:
[color=blue]
KBOYLE wrote:
[color=green]
The Xeon is Intel’s processor for servers and workstations. These
days there is very little difference in cost between a Xeon and an
equivalent desktop processor so I would go with the Xeon.[/color]
Take a look at the detailed comparison I gave of two CPUs I’m looking
at, one an i7, the other a Xeon E3. Only $30 separates the two, but
the two CPUs also look very similar spec-wise. It’s tough trying to
see what the Xeon does better that I’ll actually take advantage of in
exchange for losing some clock speed vs the i7.[/color]
It’s a common fallacy that a faster processor will produce a better
system. For example, take a 2 GHz and a 1.8 GHz processor. The
difference in speed is about ten percent. Often the cost of the faster
processor greatly exceeds ten percent of the cost of the slower
processor. Considering that most of the time a systems runs nowhere
near a hundred percent processor utilisation, all the faster processor
will do is provide a little extra headroom. It certainly doesn’t mean
that your system will run ten percent faster.
[color=blue][color=green]
Of course you’ll need an appropriate motherboard. Here too there are
important differences between server boards and desktop boards.
Server boards, even entry level ones that support a single
processor, generally can accommodate a larger RAM capacity, use ECC
RAM, can accommodate a larger IO and PCI bandwidth, provide
on-board SCSI/SAS, and are designed to run 24 x 7. Workstation
boards are similar but usually include or can accommodate high
performance graphics which aren’t needed on a server.[/color]
Generally speaking I’d say you are correct. However in this case the
max RAM supported is just 32GB either way. IO & Bandwidth look very
similar as well at least with the CPU specs. I haven’t checked ECC
capabilities so that could be one slight advantage.[/color]
Again, you’re focusing on the processor. You should be looking at an
optimal system design where there are few bottlenecks. Servers are
usually constrained by IO bandwidth and RAM limitations. Your processor
won’t be properly utilised if you can’t get the data into RAM and from
RAM to the processor quickly enough. Real server motherboards are
designed to minimise these bottlenecks. Server motherboards are
typically designed to use Xeon processors.
Servers, in general, place pretty heavy demands on disk IO and network
IO. Running a server OS on a laptop or desktop may be okay tor a demo
but, in a real world scenario, it would be very easy to swamp the PCI
bus thereby creating a bottleneck. Server motherboards have additional
PCI busses to provide additional capacity and to reduce risk of the PCI
bus becoming a bottleneck.
In virtual environments, RAM is a precious resource. Even if your
virtual servers are lightly loaded, the amount of RAM the host can
accommodate will often determine the number of VM’s you can run. 32 GB
may seem like a lot, and perhaps it is initially. If you expect to
continue using this platform for many years, I would suggest you may
want a motherboard that supports a larger capacity.
[color=blue]
And as to 24x7,
well, my current “server” is an old HP/Compaq dc5000 with a P4 CPU.
It’s been running 24x7 for many years though I’ve replaced the CPU
when I discovered the L2 cache had failed. My i7-based desktop is
nearly 4 years old now and also runs 24x7. I’ve lost one processor
in it as well, but I’m pretty sure that was a result of a power
supply fan failure I experienced earlier this year.[/color]
When designing a server, reliability and data integrity are usually key
objectives. Yes, you can use a desktop computer and it may not fail or
a failure may not affect a critical component but the risk is
greater. Server motherboards often have additional safeguards that may
not be widely publicised, like error checking on the PCI bus, to ensure
corrupted data is not written to the hard drive. Most of the time these
things are not issues on desktop systems.
[color=blue][color=green]
One other point, VMware products generally experience fewer issues
if run on approved hardware so if you have the option I would go
that route.[/color]
That’s my biggest concern. If I go a true workstation/entry-level
server board and Xeon CPU, even if it’s the E3, I’m guessing I’ll run
a lesser risk of issues with ESXi than with a desktop board and the
i7. Of course if I go with an actual used server there’s even less
risk as I can at that point check VMware hardware compatibility list.
Still, for the combined cost savings I get with both CPU &
motherboard, I’m still tempted to try the i7 route.[/color]
I would suggest you verify what OS’s are supported on any motherboard
you are considering. Manufacturers will usually specify if a particular
motherboard supports SLES, VMware, etc. They often specify the specific
releases that are supported. Again, use this information to reduce the
risk and minimise issues.
[color=blue]
BTW, here are the specs on the two CPus. You can see they are
honestly very similar to each other.
Intel Xeon E3-1245V2
http://ark.intel.com/products/65729
Intel Core i7-3770K
http://ark.intel.com/products/65523
If I could afford a decent Xeon E5 then there’d be no question I’d
just go that route. But since a decent E5 is over $400 alone
(thinking the 2620) that’s not gonna happen. Almost seems like,
then, it’s a flip of the coin going with an i7 or an E3.[/color]
IMO, comparing processor specs is of no consequence and while cost is
always an issue, determining the appropriate system configuration based
on the cost of the processor is not the way to do it.
If you can design and build your own server, if it falls within your
budget, and if you understand the tradeoffs, I say “go for it”!
Otherwise, you may be better off looking at a previously used
(refurbished) Tier 1 server. Many of these units no longer provide the
capacity needed by a large enterprise but may be more than adequate for
what you need.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are using the web interface,
show your appreciation and click on the star below…