Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>(using the answer box for space)</p> <p>Thanks for the thoughts. </p> <p>"This would make...": I deal with code that is generated from a repository. When dealing with handcoded example of this problem a developer could spot this and improve it. With generating code it's pretty hard to distill the general case from a set of examples of the problem. This can get pretty complicated so my strategy is devide and conquer. If i have to look inside the function of child that goes out the door. </p> <p>"I found this link...": I've looked at Futures, but that's more of a forking mechanism that can get parallelized when there's an idle thread. </p> <p>The TPL seems to be about splitting work up into small bits. What i want to do is take some of these bits and put them together for a while in a different composition and then split them back up again for parallel execution. (I think, still chewing on this one mentally...)</p> <p>"One more thought": Again, the devide and conquer strategy is what let me get this far. So i devide the larger problem up into little bits, solve them and then put the bits back together. I like to think of an ant colony where each ant follows simple rules (or kanban, that's a similar principle), as opposed to some central management thing (query optimizer) that gets bogged down quickly because it gets very complex very fast. </p> <p>when the parent could just call the 50 children in a parallelizable fashion, and then these seperate tasks could get batched together just because they're pointing to the same remote resource that would be great. </p> <p>The major hurdle here is how do i let the calling task (or thread or whatever, a unit of execution) block, have another one pickup the work for a batch of them, do it, put the answer into the collection where all the task put their work and them wake them up again. (and then in an efficient manner..).</p> <p>I think i remember George Chrysanthakopoulos (The guy that created the CCR) say something that the yield return statement is what he used to to such a thing. I'll try to find that interview again on Channel9. </p> <p>Regards GJ</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload