> pmap creates a future for every
> element of the sequence you give it, and that is significantly more
> computation work (allocating, initializing, and invoking future objects)
> than your function that simply returns 1 regardless of the value of its
> argument.
Makes perfect sense. Thanks for c
If I am reading your example correctly, that pmap is simply being used to
iterate over the characters of a line read into a string, then yes, you are
using pmap in a very inefficient way. pmap creates a future for every
element of the sequence you give it, and that is significantly more
computatio
Wow, just by changing pmap to map, the same code runs to completion in
1 minute 35 seconds. I'm guessing this means that context switching
caused a huge performance penalty in this case since the "work" being
executed was so miniscule?
--
You received this message because you are subscribed to th
