Concurrency and Coordination Runtime

Posted By: Charles | Dec 7th, 2005 @ 11:33 AM | 160,694 Views | 76 Comments

Formats:

The Concurrency and Coordination Runtime (CCR) is a lightweight port-based concurrency library for C# 2.0 developed by George Chrysanthakopoulos in the Advanced Strategies group at Microsoft. Here, we have a deep discussion about CCR with George, a Software Architect, and Satnam Singh, Architect. You can get more info about CCR on the CCR Wiki. This is super cool stuff and represents a really innovative approach to making managed threaded programming more readily understandable and predictable.

Please check out the OOPSLA/SCOOL paper on the CCR.

Click here to see how the CCR is being used by the Microsoft Robotics Group.

Tags: CCR, Software Composability

Rating:

DuNuNuBatman

That's good stuff, when are you guys going public with this?
Also, I think you should change the title to "Shat, I'm deadlocked" Wink

deedubb

CCR, I thought I was going to hear some good music...

I like this setup of an interviewer & seperate camera guy; keep up the good work.

Tyler Brown
Bullets change governments far surer than votes.

CCR? I was actually thinking Condition Code Registers... but I guess that's because the band was before my time. As with all other video's released lately, I've downloaded it to my file server for viewing after my last exam. Something to look forward too.

Thanks for putting out the Going Deep series Charles, I'm looking forward to it.

BuckyBit

deedubb wrote:

CCR, I thought I was going to hear some good music...

Sound: good.
Picture: good.
Questions: good.
Subject: interesting and important.
George Chrysanthakopoulos: very convincing.

Conclusion: Heck, I thought I was in the room. I love it.

mwirth

extremely interesting stuff! and the video was really fun to watch, too! reading through the paper i'm wondering how the port based ccr solution compares to the active/future objects idiom Herb Sutter is thinking about for c++0x/c++cli. did the ccr team and the guys around active<> objectives share some thoughts on the topic or are these two completely independent efforts?

again a worthy installment of going deep! nice work, Charles and Scoble!

best regards,
martin

georgioc

Hi, we developed the CCR independently from the futures work. We wanted to investigate a model where the asynchronous interaction is visible, not implicit. Futures have been around for awhile and we believe that we can express the patterns futures enable easily using ports and our basic arbiters. We are not certain having ports exposed directly is the way to go, but its a concrete, useful alternative to locks and custom one-off queuing implementations we all end up writing when we want to hook up things together.

We have discussed with Herb to see if the CCR can be the execution target for the futures/active work, assuming a native version is written. The CCR right now is only available in managed environment.

DevilsRejection
addicted to rss

Can't wait to watch this. Multicore is a very dear issue to me. It took long enough for the hardware industry to see that parrellism is the way of the future. I wonder how long until everything is distrubted computing. Imagine tapping the power of all these machine out on the planet. As I'm typing this my dual core 2gb system is barely using any of its resources, the day when our machines are always working 24/7... and quick too, that will be a nice day.

Hope Microsoft is still around, and the leader in the industry, when this paradigm shift happens.

EDIT: Just finished watching this video, this thing, combined with the Singulairty OS makes me mouth water at what OS will be out in the next decade.