You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we were not using Revise.jl in the workers. I just discovered this because as soon as I implemented it in #299 I broke everything. Apparently, as it is explained here, Revise.jl cannot handle anonymous functions in workers. We are extensively using this in pmaps, since it's the only nice way I've found to iterate over just a subset of the input arguments while keeping others fixed.
Surprisingly, the effect of not using Revise.jl in workers is not that catastrophic, meaning that I don't have the feeling the workers are recompiling everything every time there are code changes. Nonetheless, it would be interesting to find a good workaround for anonymous function usage, since I think there might be other issues involved around them.
For now, I'll just remove @everywhere using Revise from #299.
The text was updated successfully, but these errors were encountered:
Right now we were not using Revise.jl in the workers. I just discovered this because as soon as I implemented it in #299 I broke everything. Apparently, as it is explained here, Revise.jl cannot handle anonymous functions in workers. We are extensively using this in
pmap
s, since it's the only nice way I've found to iterate over just a subset of the input arguments while keeping others fixed.Surprisingly, the effect of not using Revise.jl in workers is not that catastrophic, meaning that I don't have the feeling the workers are recompiling everything every time there are code changes. Nonetheless, it would be interesting to find a good workaround for anonymous function usage, since I think there might be other issues involved around them.
For now, I'll just remove
@everywhere using Revise
from #299.The text was updated successfully, but these errors were encountered: