Add docs: cockroach debug pebble db analyze-data

[rmloveland]

Fixes DOC-15817

[netlify]

✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name	Link
🔨 Latest commit	4d5476f
🔍 Latest deploy log	https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/69729253eca52f0008753062

[netlify]

✅ Deploy Preview for cockroachdb-api-docs canceled.

Name	Link
🔨 Latest commit	4d5476f
🔍 Latest deploy log	https://app.netlify.com/projects/cockroachdb-api-docs/deploys/69729253088c2a0008bfd048

[github-actions]

Files changed:

• src/current/_includes/v26.1/sidebar-data/reference.json
• src/current/v26.1/cockroach-commands.md
• src/current/v26.1/cockroach-debug-pebble-db-analyze-data.md

[netlify]

✅ Netlify Preview

Name	Link
🔨 Latest commit	4d5476f
🔍 Latest deploy log	https://app.netlify.com/projects/cockroachdb-docs/deploys/69729253a561400008030331
😎 Deploy Preview	https://deploy-preview-22257--cockroachdb-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[rmloveland]

@RaduBerinde I think this captures the basic UX info etc from the google doc and Loom you shared. Please let me know if it is missing any important info or has inaccuracies, happy to update.

Also, q for you and @dshjoshi - I wasn't sure whether / if to say much about how best for users to approach this tool. Is the idea that they'd be working with us via Support or their assigned SEs to analyze their workloads? I would imagine most users should do this in concert with someone from CRL so they can give us feedback on possible adaptive compression designs etc? (If i read some of the internal docs right). But please let me know what you think!

[RaduBerinde]

Looks great.

[RaduBerinde]

I wasn't sure whether / if to say much about how best for users to approach this tool. Is the idea that they'd be working with us via Support or their assigned SEs to analyze their workloads? I would imagine most users should do this in concert with someone from CRL so they can give us feedback on possible adaptive compression designs etc?

Correct. The data is generally useful to us just to make further improvements, and it can also help inform changing the compression algorithm in a specific cluster. There are other things that factor into that decision (e.g. how much CPU usage headroom there is), so ideally CRL helps with that decision.

[rmloveland]

I wasn't sure whether / if to say much about how best for users to approach this tool. Is the idea that they'd be working with us via Support or their assigned SEs to analyze their workloads? I would imagine most users should do this in concert with someone from CRL so they can give us feedback on possible adaptive compression designs etc?

Correct. The data is generally useful to us just to make further improvements, and it can also help inform changing the compression algorithm in a specific cluster. There are other things that factor into that decision (e.g. how much CPU usage headroom there is), so ideally CRL helps with that decision.

ok thanks Radu! i guess this is somewhat covered under the 'Use cases' section where we say

This data can help Cockroach Labs evaluate compression defaults and can help you evaluate whether an alternate compression algorithm is appropriate for your workload.

so for now I'll leave it at that, but we can update it as needed with more words if we encounter situations where customers need clarification

thank you for the review!

[florence-crl]

lgtm pending suggestion and question.

[florence-crl]

additional suggestions

[rmloveland]

thanks for the reviews! merging now ...