Wednesday, June 04, 2008
« TechEd 2008 Day 1 Part 2 | Main | TechEd 2008 Day 2 Part 2 »

This morning’s session with Stephen Toub on the parallel extensions to the .net framework was excellent.  Stephen had a  quad-core laptop that was enormous and hotter than the surface of the sun.  Intel’s quad-core mobile chips for laptops should be out this summer.  Anyone want to buy a used Vostro with a Core2 Duo?  He also had an early prototype of a system based on the Intel Dunnington architecture that appeared to have 20 cores.  I suddenly felt that my Quad Core setup at home was hardly adequate to do real concurrency research.

I owe him several comments and I hope my notes are adequate to remember all of them.  I brought some more questions I didn’t ask yesterday.

Q: Stephen has stated that the goal is for developers to extend System.Threading.Tasks.Task in order to do concurrency at a lower level than Parallel.ForEach<>, yet Task has an internal constructor keeping you from extending it.

A: The PFX team realized this during their internal code reviews and this will be fixed in a future CTP.

Q: In the ray-tracing example, you can see one of the pitfalls of static partitioning of workload.  Compare the top of the image vs. the bottom.  In ray-tracing the objects and reflective surfaces make for much more intensive computations, and so the top of the screen draws very quickly while the bottom of the screen fills in rather slowly.  Is thought going into hinting semantics that would allow users of PFX to indicate that certain units of execution have a greater “weight” relative to others?  Would you handle this by changing priority of some Task threads so Windows gives it extra cycles, or changing the static partitioning algorithms?

A: With the current Task API, you can set the priority of a Task, which ultimately means thread priority.  There is design discussion going on related to how we might be able to give hints to the TPL.

I just got out of a “deep dive” on the Silverlight 2 rendering pipelines.  There were some good debugging hints I didn’t know about, but other than that the dive was not as technical as I’d hoped.  Right now I’m in a social networking session led by Rob Howard, and then on to more Silverlight.