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
Is your feature request related to a problem? Please describe.
Sending the problem and population to every ipyparallel engine with every evaluation is fairly slow, specially when using many (>100) engines. If the problem does not change during the evolution, it should be enough to send it only once. Additionally, it may be worth having the option to read/write the population to disk, completely avoiding the scatter step.
Describe the solution you'd like
I think I'm looking for a new bfe, that does not pickle everything every time, and that can use other ipyparallel views (such as BroadcastView). Would other aspects of pygmo have to change to enable this?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sending the problem and population to every ipyparallel engine with every evaluation is fairly slow, specially when using many (>100) engines. If the problem does not change during the evolution, it should be enough to send it only once. Additionally, it may be worth having the option to read/write the population to disk, completely avoiding the scatter step.
Describe the solution you'd like
I think I'm looking for a new bfe, that does not pickle everything every time, and that can use other ipyparallel views (such as BroadcastView). Would other aspects of pygmo have to change to enable this?
The text was updated successfully, but these errors were encountered: