Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[question] Service API low recommended parallelism
See original GitHub issueService API allows to run parallel trials. However, when reaching the threashold of acceptable number get_next_trial throws a ValueError. I was wondering if this could be changed for some more specific exception or returning None?
I want to avoid using enforce_sequential_optimization=False and get_recommended_max_parallelism is returning me a small parallel setting on default ([(5, 5), (-1, 3)]).
Any tips to either increase this number for parallel evaluations (still sequential batch evaluations)?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@casassg, we will definitely consider adding an early stopping check and see if we can develop a good heuristic for it, thank you for the suggestion!
Re: following the conversation, I will definitely describe the changes in the changelog of the repo, but maybe @kkashin has more ideas on how we could keep you in the loop!
Making this an “enhancement” and a “wishlist” item for now, since early-stopping heuristic will be part of our more long-term plan and the question part of the issue was answered.