-
Notifications
You must be signed in to change notification settings - Fork 56
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
parallal eval does not use all available workers #233
Comments
Hmm, long time since working with that code so not 100% sure here but there is a parameter that decides how many samples are done for each "round" of the NES algorithms. Probably that one might limit how many parallel executions are done. Not fully sure if it's the lambda parameter though, maybe you can try that and later today I can remind myself and see if it would really have an effect. |
bingo! 🎉 thanks for the super fast help. for reference
uses in fact 20 workers:
|
hello,
I find that I almost never am able to take advantage of all available workers on a cluster. Here I have 20 workers, but the
xnes
algorithm only ever uses 13. I also tried withdxnes
but that uses 14 out of 20. Is there anything in the algo that determines how many workers to use?i tried this:
The text was updated successfully, but these errors were encountered: