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
When implementing the migration of unit tests for quicklists, #515 . It contains a lot of benchmark code in the middle. During this period, the time consumption was counted.
We often need to quantify the effects of optimization, such as memory and time consumption. And, there should be a unified set of performance reports on different hardware.
In this way, Valkey can have a performance report, specifically targeting critical logic, and can visually see the optimization results. And there is also a standard to describe the PR for subsequent optimization.
Description of the feature
We can implement a function type starting with "bench_", referring to the Golang benchmark, which supports the number of incoming loops, and defaults to counting the number of calls, related time consumption, and memory usage.
It also supports standard format output, such as CSV.
Alternatives you've considered
Rewrite some loops within the existing testing framework
Additional information
Any additional information that is relevant to the feature request.
The text was updated successfully, but these errors were encountered:
The problem/use-case that the feature addresses
When implementing the migration of unit tests for quicklists, #515 . It contains a lot of benchmark code in the middle. During this period, the time consumption was counted.
We often need to quantify the effects of optimization, such as memory and time consumption. And, there should be a unified set of performance reports on different hardware.
In this way, Valkey can have a performance report, specifically targeting critical logic, and can visually see the optimization results. And there is also a standard to describe the PR for subsequent optimization.
Description of the feature
We can implement a function type starting with "bench_", referring to the Golang benchmark, which supports the number of incoming loops, and defaults to counting the number of calls, related time consumption, and memory usage.
It also supports standard format output, such as CSV.
Alternatives you've considered
Rewrite some loops within the existing testing framework
Additional information
Any additional information that is relevant to the feature request.
The text was updated successfully, but these errors were encountered: