Details
-
Improvement
-
Status: Resolved
-
High
-
Resolution: Fixed
-
None
-
Performance
-
Low Hanging Fruit
-
All
-
None
-
Description
Normally the CompressionInfo.db file is trivial in size (a few kb) and so can be easily cached to prevent wasteful requests for the same file, but for large SSTables (running into a few hundred GB, due to schema issues or large blobs) then the CompressionInfo.db files can also grow to be a few hundred MB or GB making it problematic to cache. We should make the compression cache optional and configurable so we don’t cache large files.
Attachments
Issue Links
- links to