Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Windows multiprocessing | Added pretty README plots | Issue with AttributeError: can't set attribute #53

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

flipdazed
Copy link

@flipdazed flipdazed commented Jun 8, 2018

img

@flipdazed flipdazed changed the title Fixed Windows multiprocessing & Issue with AttributeError: can't set attribute Fixed Windows multiprocessing | Added pretty README plots | Issue with AttributeError: can't set attribute Jun 14, 2018
@rsteca
Copy link
Owner

rsteca commented Jun 14, 2018

Do you think this is ready for a merge?

@flipdazed
Copy link
Author

flipdazed commented Jun 15, 2018

Yes I don’t plan on making more changes to do with getting it working on windows.

What I would like to do in another merge would be to change eaSimple to the CMA-ES strategy. I think it would be a lot more effective. It requires a bit of work though as the DEAP default CMA-ES strategy is only set up for continuous variables it seems.

@luded
Copy link

luded commented Jun 21, 2018

hello Alexander, thanks for fixing the code and posting examples.
It does not seem parallel processing on Evolutionary Search is working properly though.

When I run sklearn out of the box GridSearchCV I see many parallel Python process (multiple entries in Task Manager) -- as many as parallel jobs I have requested (thru n_jobs) . Incidentally I can set a number greater than my cores and If I do My Win10 machine runs at 100% CPU, as is expected.

When I switch to Evolutionary Search, and I repeat the experiment all else being equal, my task manager only shows 1 instance of python, my machine runs at very low CPU and the search takes a long time to complete.

All this seems to point to some underlying problem with the way multi processing is done by Evo Search. Do you have the same. Can you get your machine running parallel processes with Evolutionary Search?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants