multi-volume storage is a feature of ClickHouse starting in version 19.15 The idea is that you store new data on fast storage, like NVMe SSD, and move it later to slower storage, such as high-density disk. Not only does this save on storage, but you can often reduce the overall number of servers without giving up performance. It’s a double win for efficiency that can reduce hardware costs up to 80% as this example spreadsheet shows. Not surprisingly tiered storage has been a top feature request for years.
When you hear "No one needs big data", look over the CV of the speaker. An African telecoms carrier going through amazing levels of growth is not going to reach out to a greenfield JavaScript Web Developer and ask them if they could help architect their data platform and optimise their billing calculations. You might find a lot of internally-hosted web applications in an Airline's headquarters but when it comes to analysing PBs of aircraft telemetry for predictive maintenance there might not be any PHP developers on that project. Companies producing PBs of data often have a queue of experienced consultants and solutions providers at their door. I've rarely seen anyone plucked out of web development by their employer and brought into the data platform engineering space; it's almost always a lengthy, self-retraining exercise. Disks are catching up in speeds as well. There was a 4 x 2 TB PCIe 4.0 NVMe SSD card announced recently that could read and write at 15 GB/s. The price point of the PCIe 4.0 NVMe drives will be very competitive with RAM and provide non-volatile storage. I can't wait to see an HDFS cluster with some good networking using those drives as it'll demonstrate what an in-memory data store with non-volatile storage with the rich, existing tooling of the Hadoop ecosystem looks like. The migration to a columnar storage solution for this client brought down those infrastructure costs by two orders-of-magnitude and sped up querying times by two orders-of-magnitude.
New JOIN TO ONE clause in 26.2 SELECT
-
I've just published a short video on the new JOIN TO ONE clause in SELECT
statements in Oracle 26ai 26.2
This clause allows you to let the database auto...
Savepoint Funny
-
Here’s an example that makes perfect sense if you know how Oracle handles
data locking. It’s one that I thought I’d published years ago, but it’s not
on th...
NoCOUG Conference – 2/27/2026
-
Well for the first time in a very long time I am posting something on my
blog. I’m doing a keynote for the Northern California Oracle Users Group
(NoCOUG)....
Response to Make database simpler
-
I read an interesting and thought provoking blog this morning Make Oracle
database simple again Much of is is common sense and is really best
practise – n...
TIP 120 - How much memory my Linux process is using
-
_uacct = "UA-2338271-1"; urchinTracker(); Just came across some notes
regarding Linux memory and I thought to share the below tip on how to find
out memory...
We have moved!
-
You might have been wondering why things had gone so quiet on the Optimizer
development team's blog Optimizer Magic over the last few months. Well the
blog...