add thread batch evaluator

[spline2hg]

added batch evaluator that uses threading #565

[spline2hg]

I have done a simple comparison between the three evaluators in thisnotebook I noticed that the thread evaluator runs comparatively faster than the process evaluators. Could this be due to lower computational demands? Additionally, is the faster re-running due to some form of caching?

[janosg]

Hi @spline2hg which one runs faster depends on the application. A thread based batch evaluator will be faster for IO bounds functions or very fast functions due to its lower overhead. Process based batch evaluators will be good for CPU bound long running functions. But that's the whole reason why we offer multiple batch evaluators, so everyone can pick the best for their problem 🙂

[janosg]

Please also add tests for your new batch evaluator. Since the tests are already parametrized this should be as simple as adding "threading" to the list here.

[spline2hg]

just a small note the pathos batch evaluator is not added in the testing batch evaluator here, we could keep it this way if thats what we wanted, i have made the said changes, let me know if any more changes are required

[janosg]

Hi @spline2hg, thanks for the updates. I think we can leave pathos out of the tests and are going to deprecate it soon.

I enabled the CI run for your PR and there are a few failing tests. Can you look into them?

[spline2hg]

hi @janosg , sorry, i might have overlooked something. i have fixed it, and it should most likely pass the ci run.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
src/optimagic/batch_evaluators.py	73.52% <100.00%> (+12.65%)	⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[janosg]

Thanks a lot!