Hi Sivangi,

How are you doing today?, Yeah, that makes sense—Liquid Clustering automatically optimizes data layout in the background, which can add some overhead compared to Z-Ordering, where you control when optimization happens. Liquid Clustering continuously reorganizes data as new writes come in, which can make initial writes slower but improves long-term query performance. If write speed is a concern, you could try batching writes instead of frequent small updates or tweaking your cluster configuration for better performance. Also, if your workload benefits more from manual optimization, Z-Ordering might still be the better choice. Let me know what you're trying to optimize—write speed or query speed—and we can figure out the best approach!

Regards,

Brahma

We are trying to understabnd the overall behavior of liquid clustering

I would like to see your findings, we too are thinking to move our tables to liquid clustering and maybe your analysis will help. we too dont want to impact either write or read and there is no where mention that write will be impacted with liquid clustering . then why one will use this feature.