Matthew Podwysocki's Blog - All Comments

Dew Drop - May 16, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 16, 2008 | Alvin Ashcraft's Morning Dew — Fri, 16 May 2008 12:36:36 GMT

Pingback from Dew Drop - May 16, 2008 | Alvin Ashcraft's Morning Dew

re: Concurrency with MPI in .NET

Ian — Thu, 15 May 2008 19:24:33 GMT

I have a couple questions as you are planning on writing a series of these articles.

1. How do you deal with failure? With every machine you add, your mean time between failure changes. How do you recover lost work? How do you deal with a machine being unavailable?

2. How do you know your application is worth parallelizing without writing it?

3. How do you deal with a heterogenous network of machines? If you have machine A which is 2x the speed of machine B, MPI forces you to give them equal sized work. Your synchronization time it severely impacted.

4. How do you load balance?

5. How do you deal with other people running their programs on the same cluster?

6. When you are pushing the work to nodes, you are making two assumptions: The machine is available and ready for work, and you know that the machine can handle the load you are giving it. In light of the previous questions, what do you do about this? When looking at the CMSD (Cache Memory Swap Die) envelope, giving each node the same amount of work can be catastrophic.

7. What do you do for long running jobs? How to you deal with checkpointing? How much work will you loose? How much overhead is there? How hard is it to program?

re: Thinking in Concurrently in .NET

podwysocki — Tue, 13 May 2008 18:43:34 GMT

@flalar

I'm sure it is useful, but I haven't had a use case to make use of it yet. Instead, I'm focusing in message passing and such that MPI, F# and others are better at.

re: Thinking in Concurrently in .NET

podwysocki — Tue, 13 May 2008 18:42:24 GMT

@Martijn

I have looked at that, but the CCR has an interesting license to it, and doesn't make as much sense outside of Robotics Studio. I believe most people aren't using CCR due to some limitations and are recommending other solutions.

re: Thinking in Concurrently in .NET

Martijn Plijnaer — Tue, 13 May 2008 15:39:52 GMT

Take a look at the Concurrency and Coordination Runtime (CCR) in the Microsoft Robotics Developer Studio. It was written with concurrency in mind and it looks very promising.

re: Thinking in Concurrently in .NET

flalar — Tue, 13 May 2008 07:04:41 GMT

The Task Parallel library is actualle quite usefull. As of now you dont hava to write all the threading code yourself. This simplifies testing av is less errorprone.

re: Adventures in F# - F# 101 Part 2

Glenn Block — Mon, 12 May 2008 06:43:54 GMT

Enjoying this series Matthew. Unfortunately for me, I had other work I planned to do tonite, though I spent it reading your posts :)

Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew — Fri, 09 May 2008 12:50:05 GMT

Pingback from Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew

Weekly microsoft oriented crumbs #3 - Service Endpoint

Weekly microsoft oriented crumbs #3 - Service Endpoint — Fri, 09 May 2008 01:42:26 GMT

Pingback from Weekly microsoft oriented crumbs #3 - Service Endpoint

New and Notable 239

Sam Gentile — Thu, 08 May 2008 11:27:37 GMT

Trying to get in a habit of doing these when I get up and before getting into work. Design Patterns/DI