Skip to content
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

metrics: make upper limit of RPC latency larger #997

Merged
merged 1 commit into from
Oct 7, 2023

Conversation

jackysp
Copy link
Contributor

@jackysp jackysp commented Oct 4, 2023

@@ -185,7 +185,7 @@ func initMetrics(namespace, subsystem string, constLabels prometheus.Labels) {
Subsystem: subsystem,
Name: "rpc_net_latency_seconds",
Help: "Bucketed histogram of time difference between TiDB and TiKV.",
Buckets: prometheus.ExponentialBuckets(5e-5, 2, 18), // 50us ~ 6.5s
Buckets: prometheus.ExponentialBuckets(5e-5, 2, 22), // 50us ~ 105s
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for a network metrics, 50us may be too small 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some extremely great network, maybe it is possible. 😅

@disksing disksing merged commit daed9fd into tikv:master Oct 7, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The upper limit of RPC Layer Latency (metrics) should be increased
3 participants