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

Use num_search_each_probe for parallel evaluation of the objective #4

Open
taku-y opened this issue Jan 27, 2017 · 0 comments
Open

Comments

@taku-y
Copy link

taku-y commented Jan 27, 2017

Hi developers of combo,

Thanks for providing a great library. I want to use it for my projects.

I have a question about multiple evaluations at each probe. For a function f(x) which takes a long time to run, I want to compute f(x) for a number of x values in parallel. To test this, I ran tutorial.ipynb with the following modifications:

res = policy.random_search(max_num_probes=5, simulator=simulator(), 
                           num_search_each_probe=4)

# Originally, max_num_probes=80 and num_search_each_prob=1
# I expect that the total amount of computation is not changed
res = policy.bayes_search(max_num_probes=20, simulator=simulator(), score='TS', 
                          interval=5, num_rand_basis=5000, num_search_each_probe=4)

Is this the right way to do parallel computation as explained above?

And I'm concerned about actual computation time. The modified code seems slower
than the original, specifically on policy.bayes_search():

Original: 99.50355625152588 [sec]
Modified: 1856.6796779632568 [sec]

I expected the computation time is proportional to the number of evaluations of f(x),
so I don't understand the significant difference. That's why I'm wondering that I'm not correct
on using parallel evaluation.

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

No branches or pull requests

1 participant