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: timeseries dashboard pages are really slow on large clusters #30287

Closed
a-robinson opened this issue Sep 17, 2018 · 3 comments
Closed

ui: timeseries dashboard pages are really slow on large clusters #30287

a-robinson opened this issue Sep 17, 2018 · 3 comments
Assignees
@piyush-singh
Labels
A-webui-general Issues on the DB Console that span multiple areas or don't have another clear category. A-webui-scaling C-performance Perf of queries or internals. Solution not expected to change functional behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.

Comments

@a-robinson
Copy link
Contributor

I was running a 120 node cluster last week as part of TPC-C 50k testing, and the UI was really, really bogging down my browser whenever I had pages with graphs open. I believe it was a client side issue (although I'm sure that loading all the timeseries in the database isn't easy, either) given the way Chrome occasionally became unresponsive.

It didn't help that sometimes the time span selector would automatically switch from 10 minutes to 6 hours when I would reload or switch dashboards without me telling it to. I don't know what was going on there.

I realize this isn't a particularly useful issue since I didn't record any data about the slowness or track it down to anything specific, but I'm planning to spin up another such cluster again for a day this week. Is there anything you'd find useful for me to do/record then? Would you like to poke at it when it's up and running?

@couchand
@a-robinson a-robinson added C-performance Perf of queries or internals. Solution not expected to change functional behavior. A-webui Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear. labels Sep 17, 2018
@couchand couchand added A-webui-general Issues on the DB Console that span multiple areas or don't have another clear category. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption. and removed A-webui Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear. labels Sep 17, 2018
@couchand
Copy link
Contributor

I'm not surprised that there would be trouble trying to make all the per-node requests. We'll need to look at this pretty closely in the next release cycle. There will be engineering work and likely also design/product work to address. Thanks for reporting @a-robinson, no more details needed at the moment.

cc @piyush-singh

@couchand couchand changed the title UI dashboard pages are really slow on large clusters ui: timeseries dashboard pages are really slow on large clusters Sep 17, 2018
@couchand couchand added this to the 2.2 milestone Sep 17, 2018
@a-robinson a-robinson mentioned this issue Sep 17, 2018
Closed
@petermattis petermattis removed this from the 2.2 milestone Oct 5, 2018
@mrtracy mrtracy mentioned this issue Jan 15, 2019
Closed
@piyush-singh
Copy link

cc @dhartunian this came up again for a customer recently. We had some plans to tackle tech debt and refactoring this release, and I know we are thinking through possible changes to our charting library. Flagging this to be part of the consideration.

@dhartunian
Copy link
Collaborator

This was resolved via #62463 in #63087

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

@piyush-singh piyush-singh

Labels
A-webui-general Issues on the DB Console that span multiple areas or don't have another clear category. A-webui-scaling C-performance Perf of queries or internals. Solution not expected to change functional behavior. S-3-ux-surprise Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@couchand @dhartunian @petermattis @a-robinson @piyush-singh @florence-crl