Repository navigation
docs: explain logical checks for SpiceDB compute sizing - #602
Merged
Merged
Conversation
Signed-off-by: Kyle Brown <kyle.steven.brown@gmail.com>
Contributor
|
Preview deployment skipped — @kbrwn does not have write access to this repository. A maintainer can trigger a preview deployment by re-running this workflow. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Document logical checks per second as the baseline workload measure for sizing SpiceDB compute, using
spicedb_services_logical_checks_total. Explain how individual and bulk checks contribute to the counter and why representative load testing is needed to determine compute requirements.Add the guidance to the load-testing guide and link to it from the Prometheus documentation.
Testing