-
Notifications
You must be signed in to change notification settings - Fork 877
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
Support exporting configured_hz
from info server
#944
Conversation
When the `dynamic-hz` configuration option is in-use (Redis 6+), Redis will include `configured_hz` in the output of `info server`. The `hz` that is currently configured can impact Redis CPU utilization. This introduces exporting the server's current `configured_hz` value.
Pull Request Test Coverage Report for Build 10813968541Details
💛 - Coveralls |
Looks good. |
ad70547
to
3526bf7
Compare
The unit in this case is actually just |
Updated to add |
PR looks good! Can you please rebase and pull in the new changes that run the tests in Github Actions? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #944 +/- ##
==========================================
+ Coverage 80.19% 80.25% +0.06%
==========================================
Files 17 17
Lines 1974 1980 +6
==========================================
+ Hits 1583 1589 +6
Misses 306 306
Partials 85 85 ☔ View full report in Codecov by Sentry. |
When the
dynamic-hz
configuration option is in-use (Redis 6+), Redis will includeconfigured_hz
in the output ofinfo server
. Thehz
that is currently configured can impact Redis CPU utilization.This introduces exporting the server's current
configured_hz
value.