95190: ui: display more load stats on /hotranges page r=koorosh a=kvoli First two commits are from https://github.com/cockroachdb/cockroach/pull/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: https://github.com/cockroachdb/cockroach/pull/95388 resolves: https://github.com/cockroachdb/cockroach/issues/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 <email@example.com>
|6 hours ago|
|.github||1 day ago|
|build||21 hours ago|
|c-deps||3 weeks ago|
|cloud||3 days ago|
|docs||6 hours ago|
|githooks||2 weeks ago|
|licenses||3 months ago|
|monitoring||2 months ago|
|pkg||6 hours ago|
|scripts||3 days ago|
|tools||6 months ago|
|.bazelignore||7 months ago|
|.bazelrc||2 months ago|
|.bazelversion||10 months ago|
|.editorconfig||3 years ago|
|.gitattributes||9 months ago|
|.gitignore||2 months ago|
|.gitmodules||3 weeks ago|
|.node-version||10 months ago|
|AUTHORS||2 weeks ago|
|BUILD.bazel||1 month ago|
|CODE_OF_CONDUCT.md||9 months ago|
|CONTRIBUTING.md||9 months ago|
|DEPS.bzl||2 days ago|
|EXTERNAL-CONTRIBUTORS-HALL-OF-FAME.md||2 years ago|
|LICENSE||4 years ago|
|Makefile||3 weeks ago|
|README.md||7 months ago|
|TEAMS.yaml||3 days ago|
|WORKSPACE||3 weeks ago|
|dev||1 month ago|
|go.mod||2 days ago|
|go.sum||2 days ago|
CockroachDB is a cloud-native distributed SQL database designed to build, scale, and manage modern, data-intensive applications.
- What is CockroachDB?
- Starting with Cockroach Cloud
- Starting with CockroachDB
- Client Drivers
- Need Help?
- Comparison with Other Databases
- See Also
What is CockroachDB?
CockroachDB is a distributed SQL database built on a transactional and strongly-consistent key-value store. It scales horizontally; survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-consistent ACID transactions; and provides a familiar SQL API for structuring, manipulating, and querying data.
For guidance on installation, development, deployment, and administration, see our User Documentation.
Starting with CockroachCloud
We can run CockroachDB for you, so you don't have to run your own cluster.
See our online documentation: Quickstart with CockroachCloud
Starting with CockroachDB
- Install CockroachDB: using a pre-built executable or build it from source.
- Start a local cluster and connect to it via the built-in SQL client.
- Learn more about CockroachDB SQL.
- Use a PostgreSQL-compatible driver or ORM to build an app with CockroachDB.
- Explore core features, such as data replication, automatic rebalancing, and fault tolerance and recovery.
CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.
- For recommended drivers that we've tested, see Install Client Drivers.
- For tutorials using these drivers, as well as supported ORMs, see Example Apps.
- CockroachCloud - Steps to create a free CockroachCloud cluster on your preferred Cloud platform.
- Manual - Steps to deploy a CockroachDB cluster manually on multiple machines.
- Cloud - Guides for deploying CockroachDB on various cloud platforms.
- Orchestration - Guides for running CockroachDB with popular open-source orchestration systems.
- CockroachDB Community Slack - Join our slack to connect with our engineers and other users running CockroachDB.
- CockroachDB Forum and Stack Overflow - Ask questions, find answers, and help other users.
- Troubleshooting documentation - Learn how to troubleshoot common errors, cluster setup, and SQL query behavior.
- For filing bugs, suggesting improvements, or requesting new features, help us out by opening an issue.
Building from source
See our wiki for more details.
We welcome your contributions! If you're looking for issues to work on, try looking at the good first issue list. We do our best to tag issues suitable for new external contributors with that label, so it's a great way to find something you can help with!
See our wiki for more details.
Engineering discussions take place on our public mailing list, firstname.lastname@example.org. Also please join our Community Slack (there's a dedicated #contributors channel!) to ask questions, discuss your ideas, and connect with other contributors.
When contributing to a CockroachDB feature, you can find the relevant license in the comments at the top of each file.
For more information, see the Licensing FAQs.
Comparison with Other Databases
To see how key features of CockroachDB stack up against other databases, check out CockroachDB in Comparison.
- Tech Talks (by CockroachDB founders, engineers, and customers!)
- CockroachDB User Documentation
- The CockroachDB Blog
- Key design documents