Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
95190: ui: display more load stats on /hotranges page r=koorosh a=kvoli First two commits are from #95388. Previously the hot ranges page only showed one statistic that helped identify high load ("hot") ranges: queries per second (QPS). QPS is a measure of the number of batch request a replica processed per second, averaged over the last 30 minutes. If the batch request composition is non-uniform in terms of incidental load on the cluster, the correlation between QPS and importance of a range to the end user weakens. This commit adds more statistics per-range to the hot ranges ui page to provide better insight into load composition. The statistics are rated (per-second) and averaged over the last 30 minutes, the same as the existing load statistic QPS. - CPU: CPU time used in processing this range. - Write (keys): number of keys written on this range. - Write (bytes): number of bytes written on this range. - Read (keys): number of keys read on this range. - Read (bytes): number of bytes read on this range. The ranges that are displayed on the hot ranges page can be ordered using these statistics as a key. An example page view is shown below running kv50. ![image](https://user-images.githubusercontent.com/39606633/213811279-07348a81-05dd-463f-a970-706083c681c3.png) depends on: #95388 resolves: #95386 Release note (ui change) Add write bytes, write keys, read bytes, read keys and cpu statistics to the `/hotranges` db-console page. These statistics are the rated average over the last 30 minutes. Co-authored-by: Austen McClernon <austen@cockroachlabs.com>
- Loading branch information
Showing
10 changed files
with
197 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.