On TechRepublic: Windows 7 keyboard shortcut cheat sheet
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 2 of 10:
Next »
« Previous
Exchange & MS Virtualization
Since Exchange 2007 is being released as a 64 bit only edition, it's reasonable to assume M$ is actively working to make Exchange more compatible with multi-core systems. With that said though, my guess is that you're overstating the difficulty of making this leap. Exchange has been multi-threaded capable for quite some time now. Isn't it more of an OS thing than application limitations to reach every high numbers of cores? As long as the applicaiton is multi-threaded, how does an application really about cores? It's up to the OS to schedule threads. As long as the OS supports the significant increase in paralleled execution of threads because the cores in a single processor is growing, again why is this something an application has to concern itself with? M$ does a great job of self-tuning applications. As Intel / AMD and the server manufacturers ramp up four way and 8 way four core systems, how does this differ from running an 8 / 16 / 32 or 64 processor box? This is something MS has been supporting for three years now with Server 2003.

If however there really is a lot of applicaiton plumbing to rework with going from 1 to 2 to 4 to 8 to the recently announced 80 core test system Intel is now demonstrating, then who better is ready for this switch than M$? Under the cover a lot of what Exchange does is built on top of the JET DB engine. With M$ delaying WinFS, once can assume that this realase of Exchange may well be the last one to ride on top of JET versus something like an optimized SQL Server engine that contains many of the WinFS features M$ suggests its now backing into SQL Server.

So the answer to the previous questions is that JET will probably be replaced with a future version of SQL Server that will be optimized for this sort of grid computing that's been involving now for three years or so.

And finally, M$ is taking large strides with its virtualization product. As the hypervisor becomes available, M$ virtualization product in the server space will continue to catch up with VMWare and will mean less and less need to run this huge systems with VMWare / Linux as the VM engine.
Posted by: jjworleyeoe   Posted on: 11/30/06 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

For The Record  mighetto | 11/30/06
Exchange & MS Virtualization  jjworleyeoe | 11/30/06
5.5  KTLA | 11/30/06
CommuniGate Pro  mighetto | 11/30/06
Falling flat  KTLA | 12/01/06
Its Frank Luis Mighetto not Lewis  mighetto | 12/01/06
Good times...  KTLA | 12/01/06
Assumption about IBM  Anton Philidor | 11/30/06
Hannover  Richard Flude | 11/30/06
Wow! Features on par with...  Spikey_Mike | 11/30/06

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

  • Thought-provoking progressive ideas on diverse topics that intersect with technology, business, and life, and matter to the world at large. Visit SmartPlanet
  • More from IBM
  • Innovate your business' process model, play against the market, compete against others on our scoreboards and WIN! Try INNOV8 2.0: A BPM Simulator
  • Enabling Real-World Business Transformation through IBM Service Management Read the EMA Analyst Report
Click Here