Compression in ClickHouse – Altinity | The Enterprise Guide ...
altinity.com › 11 › 21Nov 21, 2017 · For ultra fast disk subsystems, e.g. SSD NVMe arrays, even LZ4 may be slow, so ClickHouse has an option to specify ‘none’ compression. It is possible to have different compression configuration depending on part size. I.e. use faster LZ4 for smaller parts that usually keep hot data and allow for better zstd compression for historical data ...
Do-It-Yourself Multi-Volume Storage in ClickHouse – Altinity ...
altinity.com › blog › 2019/3/5Mar 05, 2019 · Many applications have very different requirements for acceptable latencies / processing speed on different parts of the database. In time-series use cases most of your requests touch only the last day of data (‘hot’ data). Those queries should run very fast. Also a lot of background processing actions happen on the ‘hot’ data--inserts, merges, replications, and so on. Such operations ...
Amplifying ClickHouse Capacity with Multi-Volume Storage ...
altinity.com › blog › 2019/11/27Nov 27, 2019 · As longtime users know well, ClickHouse has traditionally had a basic storage model. Each ClickHouse server is a single process that accesses data located on a single storage device. The design offers operational simplicity--a great virtue--but restricts users to a single class of storage for all data. The downside is difficult cost/performance choices, especially for large clusters.