You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An interesting observation here is that each level is an order of magnitude large than the previous one. EG: 300 MB, 3 GB, 30 GB, 300 GB, etc.
This method of SST sizing could have benefits to our system. In addition this is another instance in which it would be better if we tracked sizes by bytes rather than number of records.
The text was updated successfully, but these errors were encountered:
This article discusses the size of SST levels in Rocks DB: https://vinodhinic.medium.com/lets-rock-3a73fbc6ea79
An interesting observation here is that each level is an order of magnitude large than the previous one. EG: 300 MB, 3 GB, 30 GB, 300 GB, etc.
This method of SST sizing could have benefits to our system. In addition this is another instance in which it would be better if we tracked sizes by bytes rather than number of records.
The text was updated successfully, but these errors were encountered: