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.

Sign up for GitHub

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

Jump to bottom

ui: latency hits apparent reporting limit of 10s #36543

Closed
awoods187 opened this issue Apr 4, 2019 · 2 comments
Closed

ui: latency hits apparent reporting limit of 10s #36543

awoods187 opened this issue Apr 4, 2019 · 2 comments
Assignees
@piyush-singh
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. X-stale

Comments

@awoods187
Copy link
Contributor

It appears as if we hit a limit on reported latency:
image

Perhaps this is due to sampling of the query stats?
Perhaps its due to another sampling constraint?

Either way it looks like we are underreporting here.
@awoods187 awoods187 added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. labels Apr 4, 2019
@vilterp
Copy link
Contributor

vilterp commented Apr 4, 2019

I think this is a known issue with our histograms; remember Matt T mentioning it. Can't find the issue at the moment though.

@ajwerner ajwerner mentioned this issue May 10, 2021
Closed
@github-actions
Copy link

github-actions bot commented Jun 4, 2021

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
5 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@piyush-singh piyush-singh

Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. no-issue-activity S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. X-stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vilterp @piyush-singh @awoods187