Add microbenching test harness - #41
Merged
Merged
Conversation
Owner
|
Thank you for your contribution 🎉 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Per the discussion we were having in issues - I thought about maybe doing something with testcontainers + rabbitmq to do a more realistic test, but did a survey of how some other libraries were doing it, and this seems like a pretty light weight and extensible approach.
I figure I could PR this very basic test, then if we want to extend it or focus more specifically on testing the mailbox we could talk about what kinds of microbenchmarks that would be useful, and then if this lands on main, ill update the other PR and take a look at how changing the queue implementation impacts those benchmarks.
Also: