You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current benchmarks are enough to see performance difference of any code changes. However they do not meet all requirements of real-world benchmarks.
Since we are running benchmarks sequantial, the benchmarks do not get affected by mutex or other concurrent blocker events. And this may cause not to see drawbacks of some code changes on benchmarks. This is why we have to add parallel benchmarks, especially for performance-intensive sections like router.
Impact on the Project
It will make code review easier to see performance impactions of mutex etc.
Additional Context (optional)
No response
Checklist:
I have confirmed that this maintenance task is currently not being addressed.
I understand that this task will be evaluated by the maintainers and prioritized accordingly.
I am available to provide further information if needed.
The text was updated successfully, but these errors were encountered:
Maintenance Task Description
Current benchmarks are enough to see performance difference of any code changes. However they do not meet all requirements of real-world benchmarks.
Since we are running benchmarks sequantial, the benchmarks do not get affected by mutex or other concurrent blocker events. And this may cause not to see drawbacks of some code changes on benchmarks. This is why we have to add parallel benchmarks, especially for performance-intensive sections like router.
Impact on the Project
It will make code review easier to see performance impactions of mutex etc.
Additional Context (optional)
No response
Checklist:
The text was updated successfully, but these errors were encountered: