InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

256 Core SQL Server

Posted by Jonathan Allen on Nov 12, 2008

Sections
Architecture & Design,
Development,
Operations & Infrastructure
Topics
Performance & Scalability ,
.NET ,
SQL Server
Tags
SQL Server 2008

The current version of Windows has a hard limit on the number of logical processors it can support. For the sake of this discussion a computer has (CPUs X cores per CPU) logical processors; double that if using hyper-threading. This limit Windows actually supports is 32 logical processors on a 32-bit OS and 64 logical processors on a 64-bit OS. Most of these limits are subtle constraints based on data structures. For example, processor affinity, which determines which processors a thread can run on, is expressed as a 32- or 64-bit integer acting as a bitmask.

With SQL Server code named "Kilimanjaro" and Windows Server 2008 R2, the soft limit has been raised to 256 logical processors. The theoretical maximum is much higher, but Microsoft doesn’t want to support it until they have the ability to test it.

RelatedVendorContent

Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL

Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing

Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat

Monitor your Production Java App - includes JMX! Low Overhead - Free download

Spring Data Neo4j Tutorial

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.