We have a 6 node cluster.
Yugaware interface shows “SST” & “uncompressed SST” column for every node(as shown below):
What is SST? uncompressed SST?
We have a 6 node cluster.
Yugaware interface shows “SST” & “uncompressed SST” column for every node(as shown below):
What is SST? uncompressed SST?
Hi, tables and indexes are stored in SST (Sorted Sequence Table) files. “Total SST Files Size” is the size on disk of those files, the total is the physical size of the database. There are various levels of data compression and the “Uncompressed SST Files Size” is the size before compression, so the logical volume of the data (tables and indexes).
An example looking at the size of tables here:
@FranckPachot
When query is submitted by GoCQL driver to yugabyte,
In terms of usage(for query processing), How RAM memory different from SST files?
The client driver/language doesn’t matter. Irrespective of the client language (whether it is Go/PHP/Python/Java)… YugabyteDB brings/needs to have the relevant portions of data into RAM. The data (both metadata - such as index, bloom filters, and the user data or rows) live in SSTable files are composed of smaller blocks (say 32K or 64K sized blocks). YugabyteDB has a on-demand block cache… and doesn’t require all data to be resident in RAM… it basically automatically keeps only the hot data in cache. Therefore, YugabyteDB can generally work quite well even if RAM size is much smaller than the data set size. Even for workloads that do fairly random reads in a way that the entire data set doesn’t fit well in RAM… YugabyteDB is pretty optimal in terms of the number of disk seeks it ends up doing. See for example: Achieving Sub-ms Latencies on Large Datasets in Public Clouds | Yugabyte.
@FranckPachot
Is SST file of yugabyte similar to WAL file of TSDB(in Prometheus)?
I just had a quick look at TSDB and it doesn’t map exactly but SST Files are not WAL.
So, if you create a table with few rows, you will still see a zero size for SST Files because it is all in MemTable and WALs are not counted there. After some more writes, you will see the SST Files increasing, in number and then in size. And at some point, the total size will be decreasing after compaction. But it is roughly the size of your data on disk. The uncompressed size gives an idea of the size of them if they were not compressed, so roughly the logical size of your data.