Druid vs Rockset Revisited

Mar 05, 2021
Alan Li

Rockset recently published a blog post that compared the performance of Apache Druid 0.18 versus Rockset using the SSB benchmark. Druid 0.18 is about 9 months out of date at this point, so we wanted to revisit the benchmark based on the latest version of Druid (0.20.1), which includes several performance improvements we’ve been doing over the last few months.

Our findings are below:

QueryImply3.3.0Imply 2021.02Rockset
Q1.11245462944
Q1.2155154254
Q1.392160296
Q2.1662139161
Q2.2591102136
Q2.331979129
Q3.1292333626
Q3.2514102598
Q3.341791343
Q3.41007232
Q4.1883179384
Q4.2389109132
Q4.33848741
 604320694076

We can see a remarkable improvement in performance with the latest version of Druid. Two main things drove most of the change:

1) Many of these queries in the SSB benchmark use expressions. In older versions of Druid, we did not have vectorized expressions implemented, so many of the queries couldn’t vectorize. In the latest version, 100% of these queries vectorize.

2) The schema used to ingest data was changed to match what Rockset is doing. Similar to how Rockset “specified some keys for column-based clustering”, we also used column based clustering (in Druid it’s called partitioning). No further tuning was done in Druid.

In our next release of Druid, we are releasing another set of performance improvements. Stay tuned for more information.

Other blogs you might find interesting

No records found...
May 21, 2026

A First Look at Lumi Loglake: Query Logs Where They Live

TL;DR: Imply Lumi Loglake is a lakehouse (separated compute/storage) architecture for unstructured logs that reduces costs from 40% up to orders of magnitude on your hardware/AWS/Azure bill used to run your...

Learn More
May 11, 2026

Imply Lumi Major Release Preview: Continuing the Journey Towards Decoupled Observability/SIEM

We are getting ready to introduce the next major expansion of Imply Lumi and the observability warehouse. When we introduced the industry’s first observability warehouse, the goal was clear: decouple the...

Learn More

Ready to decouple your observability stack?
No workflow changes. No migrations. More data, less spend.

Request a Demo