First, my apologies for any delay in getting your questions answered. We have an new support community, http://communities.intel.com/community/tech that just launched in order to better respond to questions such as yours.
At any rate, let me point you to some information that may be helpful in your decision. This is an interesting comparison because you are looking at one product E3110 which is an entry level, single CPU server processor and a desktop processor, the Core 2 Duo.
Please follow this link for the XEON E3110 processor: http://ark.intel.com/cpu.aspx?groupId=34694
And this link for the E8400 C2D: http://ark.intel.com/cpu.aspx?groupId=33910
Please let us know if this has been helpful for you.
would you suggest to post my question in this section again?
i compared those CPUs already.
from my point of view the main differences, according to the summary informations, are:
"Intel Trusted Execution Technology" and "Intel Stable Image Platform" - otherwise i couldn´t spot other differences between those CPUs
(except for the Core Voltage)
let me put it this way: what makes the E3110 "an entry level, single CPU server processor" as you stated in your post?
am i overlooking something?
in a specification-sheet, the C2D was called a "client processor", could you throw some light on this maybe?
1 of 1 people found this helpful
Now we are getting closer to the answer you are looking for.
In general, desktop and server platforms follow different roadmaps, meaning the lifecycle and feature set can vary. In this case, two technologies are offered for the client processor (C2D) and are not part of the server processor (E3110). In the case of Intel Trusted Execution Technology (TXT), this feature did not make it into the server product due to future product considerations, and often is a matter of timing for the product teams.
Are you familiar with TXT? This is a software feature that adds an addional layer of code between the hardware and the OS or VM, essentially allowing the user to better control the software stack. Mostly you would see this implementation in business environments (Regulated Industries, IT Departments) where maintaining strict security policies are a high priority as well as knowing just what software is actually running for any given system.
As for the Stable Image Platform Program (SIPP) feature, the difference is the lifecycle for ongoing support and availability. In some cases, an IT dept. may be interested to maintain a longer life cycle and SIPP supports this by extending the lifecycle of a given processor or platform. Imagine a scenario where the IT dept. wants to maintain the exact configuration for longer than 2 years. This is where SIPP comes in.
Another differentiating feature of server platforms is support for ECC memory and the vailidation of such. In some cases, the client counterpart may support ECC, but is not necessarily validated in the same ways. Also, server validation would include enterprise server OS validation whereas the client counterpart would not.
Are we getting any closer to answering your questions?
Wm. Hank Lea
thanks for your detailed elaboration william,
for my personal needs, these two features (TXT and SIPP) are not quite important to me.
it is just about a fileserver (SOHO) with approximately 5 clients, but it has to ran 24/7 rockstable.
mainboard is an Intel S3210SHLC with 4x1Gb DDR2 ECC Micron, so according to you a Xeon CPU, like the E3110, would offer me a better ECC support?
reliability is definitive the main focus here.
we are getting closer now i think
Yes, the E3110 provides ECC support for DDR2 memory you mention. You may want to read the Product Brief if you are interested.
Hope we have been helpful, and please let us know if you have other questions.
ECC support should be chipset dependant, right? so i would have ECC in both ways with my Intel S3210SHLC board (C2D and Xeon CPU)
i was refering to your quote: "Another differentiating feature of server platforms is support for ECC memory and the vailidation of such. In some cases, the client counterpart may support ECC, but is not necessarily validated in the same ways."
so i´m not asking if the Xeon supports ECC, but in what way the Xeon offers "better" ECC support over a client processor like the C2D?
does it make a Xeon CPU the better choice for 24/7 use?
Good point. The way I understand the differences is a matter of validation. As you might imagine, we cannot validate every possible combination. For the Server CPU, my understanding is the ECC memory cabability is part of the validation process with Server OS, whereas, this would not be the case for the desktop as the validation matrix would look different. Does that make sense?
1 of 1 people found this helpful
Thanks again for your patience as we make sure to get the best answer we can for you. I've been discussing this amongst some of the Intel experts and here's an update from my last reply.
Really, in this generation is it an advocacy position - we advocate the Xeon CPU in server operating systems due to a separate validation process that take place with them. Client CPUs do not go through the same level of validation in these OSes as the Xeon CPUs do.
As to your question on what makes the processors suited for Server or Desktop we see the primary difference between these CPUs is the level of testing and validation with different operating systems and with difference configurations. The Intel Xeon E3110 processor is fully tested and validated predominantly with server operating systems with typical server configurations, such as with ECC memory. Check out this link: S3200SH Motherboard
for a list of tested operating systems for this specific motherboard.