-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Benchmark #68
Benchmark #68
Conversation
Hello we have another feature: runtime-tokio which doesn't use async-std. Is there a general solution? |
I can implement a small Basically we need to be able to run the benchmarks with |
Hmm it actually does seem to make some difference, but it would be more "real world" accurate to use tokio or async-std. I'll push both option so you can look it over.
this is run with async-std against the simple |
Codecov Report
@@ Coverage Diff @@
## master #68 +/- ##
=======================================
Coverage 80.46% 80.46%
=======================================
Files 18 18
Lines 2580 2580
=======================================
Hits 2076 2076
Misses 504 504 Continue to review full report at Codecov.
|
LGTM! and thanks for your great work. |
Add
criterion
bench marking for someEnforcer
methods and constructor. I would imagine there are more methods and features to benchmark just let me know!Starts to complete
benchmark
#5 in roadmap.