[ty] Re-enable multithreaded pydantic benchmark #19176
Merged
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.
Summary
I played with those numbers a bit locally and
sample_size=3, sample_count=8seemed like a rather stable setup. This means a single sample consistents of 3 iterations of checking pydantic multithreaded. And this is repeated 8 times for statistics. A single check took ~300 ms previously on the runners, so this should only take 7 s.