Parallelism at PDC: Day 3 - Concurrency Runtime - InformationWeek
IoT
IoT
Mobile // Mobile Applications
Commentary
10/28/2008
12:00 AM
Commentary
Commentary
Commentary
50%
50%
RELATED EVENTS
Moving UEBA Beyond the Ground Floor
Sep 20, 2017
This webinar will provide the details you need about UEBA so you can make the decisions on how bes ...Read More>>

Parallelism at PDC: Day 3 - Concurrency Runtime

Niklas Gustafsson gave a "Deep Dive" talk on Microsoft's Concurrency Runtime. The Concurrency Runtime is a key feature in Microsoft's Visual Studio 2010.

Niklas started his talk by warning people it was a deep dive C++ oriented talk, one without glitz or performance data - but rather education and coding. A number of non-C++ programmers left the room appreciative of the 'heads-up' at the outset of the class. Niklas got a well deserved round of applause for his clarity.

Niklas invited me to join him on stage an talk about why we've been vocal at Intel about supporting Concurrency Runtime.  In August, we went as far as to announce our support of this at the same time we announced our Intel Parallel Studio project.

I explained that year ago we consolidated on use of our own OpenMP runtime after some time of experimenting with various forms of parallelism in our math library vs. our compiler's implementation of OpenMP.  Then, along came Intel Threading Building Blocks (TBB).   For various reasons, TBB implemented it's own scheduler and thread pool completely separately from OpenMP.  Next, Microsoft added to the mix with their own OpenMP in their compiler complete with their own solution for a thread pool.  Throw in another threading package and you could quickly have 4X the software threads as you have hardware threads.  Consider a two processor Intel Core I7 system, each being an 8-core, 16-thread processor.  4X subscription would mean a program creating 128 software threads for 32 hardware threads.  The resulting pressure on memory and stacks will be unacceptable.  We can survive with 2X on 2 core processors... but somewhere on the way to 64 hardware threads we will have a problem when programmers use more than one programming model.

If nothing else, threaded libraries make this a problem we must solve. Along comes Microsoft Concurrency Runtime.

Niklas walked us through the infrastructure  that enables multiple concurrent programming models by allowing definition of multiple work schedulers working together with a central resource management system.

Microsoft's Concurrency Runtime encourages innovation at library and tool levels while solving key issues which would have been a big headache.

 

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
How Enterprises Are Attacking the IT Security Enterprise
How Enterprises Are Attacking the IT Security Enterprise
To learn more about what organizations are doing to tackle attacks and threats we surveyed a group of 300 IT and infosec professionals to find out what their biggest IT security challenges are and what they're doing to defend against today's threats. Download the report to see what they're saying.
Register for InformationWeek Newsletters
White Papers
Current Issue
IT Strategies to Conquer the Cloud
Chances are your organization is adopting cloud computing in one way or another -- or in multiple ways. Understanding the skills you need and how cloud affects IT operations and networking will help you adapt.
Video
Slideshows
Twitter Feed
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Flash Poll