Title: Improve Summary quantiles with DataSketches · Issue #2084 · prometheus/client_java · GitHub
Open Graph Title: Improve Summary quantiles with DataSketches · Issue #2084 · prometheus/client_java
X Title: Improve Summary quantiles with DataSketches · Issue #2084 · prometheus/client_java
Description: Summary.observe() can become expensive when quantiles are recorded at high frequency. This can make the current quantile path visible on hot request paths. We saw this in ZooKeeper's Prometheus metrics path. In an internal ZooKeeper 3.9....
Open Graph Description: Summary.observe() can become expensive when quantiles are recorded at high frequency. This can make the current quantile path visible on hot request paths. We saw this in ZooKeeper's Prometheus met...
X Description: Summary.observe() can become expensive when quantiles are recorded at high frequency. This can make the current quantile path visible on hot request paths. We saw this in ZooKeeper's Prometheus...
Opengraph URL: https://github.com/prometheus/client_java/issues/2084
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve Summary quantiles with DataSketches","articleBody":"`Summary.observe()` can become expensive when quantiles are recorded at high frequency. This can make the current quantile path visible on hot request paths.\n\nWe saw this in ZooKeeper's Prometheus metrics path. In an internal ZooKeeper 3.9.2 fork, a version inspired by ZooKeeper's unmerged DataSketches Summary [PR](https://github.com/apache/zookeeper/pull/2086) improved peak throughput by about 2x.\n\nDataSketches KLL may be a useful way to improve this in `client_java`. The goal would be to reduce the cost of the observe path while keeping the external Summary behavior as close as practical.\n\nThis would not have to replace the current CKMS-based `Summary` immediately. DataSketches KLL has a different accuracy model, memory cost, and quantile visibility behavior, so an explicit opt-in path may be a better first step.\n\nInitial questions:\n\n- Does using DataSketches for Summary quantiles sound like a direction worth exploring?\n- If so, would a separate opt-in artifact be a reasonable way to introduce it?\n- What behavior details and benchmark data would be most useful before going further?\n","author":{"url":"https://github.com/DCjanus","@type":"Person","name":"DCjanus"},"datePublished":"2026-05-01T10:59:45Z","url":"https://github.com/prometheus/client_java/issues/2084"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:6028c9cc-3624-78f5-47d2-471d2996b08c |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D710:ABEA3:1F288F:293D9F:6AFBB348 |
| html-safe-nonce | d70a8df74c083106c922d4a91a733beffd5d0549a28e5e58ab83ab2634d2f79b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENzEwOkFCRUEzOjFGMjg4RjoyOTNEOUY6NkFGQkIzNDgiLCJ2aXNpdG9yX2lkIjoiNDM2MzE1NTY3MTc1OTk1ODg1NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 4b540d998dbd104070547d52d20d6db512f8a111ef0985d9ffaf7d5d9d538a0b |
| hovercard-subject-tag | issue:4364053057 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/prometheus/client_java/2084/issue_layout |
| twitter:image | https://opengraph.githubassets.com/73f39ce48dc48cfb0813214f8d218416f5a91f6c39008d8902e5f4f0caa2819a/prometheus/client_java/issues/2084 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/73f39ce48dc48cfb0813214f8d218416f5a91f6c39008d8902e5f4f0caa2819a/prometheus/client_java/issues/2084 |
| og:image:alt | Summary.observe() can become expensive when quantiles are recorded at high frequency. This can make the current quantile path visible on hot request paths. We saw this in ZooKeeper's Prometheus met... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | DCjanus |
| hostname | github.com |
| expected-hostname | github.com |
| None | 2b2ef9c1578c18d8ed27027940544c958743213cf4461659f14d3ccdf51e162c |
| turbo-cache-control | no-preview |
| go-import | github.com/prometheus/client_java git https://github.com/prometheus/client_java.git |
| octolytics-dimension-user_id | 3380462 |
| octolytics-dimension-user_login | prometheus |
| octolytics-dimension-repository_id | 7997879 |
| octolytics-dimension-repository_nwo | prometheus/client_java |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 7997879 |
| octolytics-dimension-repository_network_root_nwo | prometheus/client_java |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | e4cce0e99cf61481a318ff12c2e8580153a6c7c6 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width