Add more (high-level) details about Pebble compression features#23245
Add more (high-level) details about Pebble compression features#23245rmloveland wants to merge 2 commits intomainfrom
Conversation
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| The output CSV file is periodically rewritten while the command is running. Even if the command is interrupted, you can still use the most recently written output. | ||
|
|
||
| ### Interpret results |
There was a problem hiding this comment.
I don't think we should encourage customers to interpret these results in their current form. We should say that they should just consult us with the data.
There was a problem hiding this comment.
i have revised this section a bit with a new title, and clarified that the output is not really designed for end users, and they should contact Support - hope it's clearer now, please let me know!
|
|
||
| Changing `storage.sstable.compression_algorithm` does not immediately recompress existing SST files. SSTs are immutable, so a new setting applies as Pebble writes new SSTs or rewrites existing SSTs during compaction, ingestion, restore, or other SST-writing work. During a transition, a store can contain SSTs compressed with multiple algorithms. | ||
|
|
||
| To evaluate the compression behavior of an existing store or backup, use [`cockroach debug pebble db analyze-data`]({% link {{ page.version.version }}/cockroach-debug-pebble-db-analyze-data.md %}). Compare the compression ratio with the compression and decompression throughput for representative data before changing the cluster setting. |
There was a problem hiding this comment.
I'd say "To evaluate the CPU usage vs size tradeoff on your particular data, use .."
There was a problem hiding this comment.
updated! based on your other comment about not encouraging users to change this themselves, i also updated the second sentence to clarify that they should review the results with us before changing the cluster setting
To evaluate the CPU usage vs. size tradeoff for your particular data, use [
cockroach debug pebble db analyze-data]({% link {{ page.version.version }}/cockroach-debug-pebble-db-analyze-data.md %}). Review the results with Cockroach
Labs Support before changing the cluster setting
|
thanks for the review @RaduBerinde - i have updated to address your feedback, PTAL! |
2 participants
Fixes DOC-16758