5 ms·

Thanks! From the documentation and all the threads I searched in discourse, it was never clear to me that @parallel and pmap where aiming towards the direction

Thanks! From the documentation and all the threads I searched in discourse, it was never clear to me that @parallel and pmap where aiming towards the direction you just described. I did try Threads.@threads, but the overhead was way too high. I might look into it again soon.

wallnuss 9y ago
Threads.@threads is still consider a bit experimental and there are a few performance pitfalls that one can stumble into. I talked about this for a bit in http://slides.com/valentinchuravy/julia-parallelism http://slides.com/valentinchuravy/julia-parallelism, but if you still have issues after reading that feel free to reach out on https://discourse.julialang.org https://discourse.julialang.org and we will figure out what is going on.
- xiaodai 9y ago
  Very technical presentation, but it contains nuggets of that I can't wait to try once I get home! Do you have a blog that lays this out in a way that is aimed at the general Julia programmer?
  - wallnuss 9y ago
    Working on it :) I will probably announce it on twitter (@vchuravy) once I managed to find time to finish it.
- xiaodai 9y ago
  unfortunately slides.com is blocked at work....
ChrisRackauckas 9y ago
The problem isn't overhead but that there's a performance bug that one can easily hit with multithreading right now, which is why it's labelled experimental. When that's fixed hopefully you'll be happy :). A function barrier fixes it, but it's a little nasty. This is probably the bug I want fixed most, but since it's not syntax breaking it's a slated for v1.x and not v1.0.