News

Microsoft Releases Beta of High-Performance Computing Server

Microsoft took the next step into the arena of high-performance computing (HPC) today when it announced the release of the first beta of Windows HPC Server 2008, the successor to Compute Cluster Server 2003.

The public beta was scheduled to be available here; as of presstime, however, no download was listed on the Website. The final version is expected to be generally available in the second half of 2008, Microsoft said in a press release.

The product was renamed, Microsoft said, "to reflect its readiness to tackle the most challenging HPC workloads". HPC Server 2008 is based on Windows 2008, slated for availability early next year; it will be a specially-crafted version meant to run on large clusters. Microsoft revealed few details of the server, but did list a number of key features, including a service oriented architecture (SOA) job scheduler; support for partners' clustered file systems; better failover capabilities; more efficient and scalable management tools; and high-speed networking.

Kyril Faenov, general manager of HPC at Microsoft, said in the release that Redmond has seen substantial gains in its HPC environment from the new server. "By upgrading to Windows HPC Server 2008 on our 2,048-core production test cluster, we increased the LINPACK performance by 30 percent and were able to deploy and validate the cluster in less than two hours using out-of-the-box software. Expanding beyond traditional MPI [Message Passing Interface]-based HPC applications, Windows HPC Server 2008 enables support for high-throughput SOA applications with its advanced Web service routing capability and paves the way for bringing HPC capabilities to a broad range of enterprise applications."

LINPACK is a software program that solves high-level mathematical equations. It's frequently used as a benchmark for computing power and performance.

Five years is a long time in the computer age for a new server release, but HPC Server 2008 has followed nearly the same timeline as Windows 2008, which will be released about five years after Windows Server 2003. Until Compute Cluster Server 2003's arrival on the scene, Microsoft had largely been frozen out of the HPC space. It was dominated by "big iron" and more scalable OSes like Unix and Linux.

HPC is still largely confined to the realm of science, engineering and medical and other research; many of the largest computer clusters are found at research universities. The trend over the last few years has been to put more cores on processors and more processors on chips, as it's been getting more and more difficult to squeeze additional performance out of a single processor.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube