Add async support for dspy.Evaluate #8504
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are introducing:
_execute_with_multithreading
for running evaluation in multithreading_execute_with_event_loop
for running evaluation in async concurrency.The weird part is although technically async eval should run faster than multithreading because evaluation is IO bound task, but I am not noticing it consistently.
Testing script is pasted below:
70% time async runs faster than multithreading insignificantly, and 30% time it's the reverse. Two potential theories: