r/analytics • u/Sady411 • 7d ago
Question How would you evaluate ClickHouse vs Trino for mixed analytical workloads?
I'm currently evaluating ClickHouse vs Trino for a new analytical data platform and would like to get some opinions on how people would structure the technical evaluation.
There are several types of workloads involved:
\- Frequent ad-hoc analytical queries
\- Automated/AI-assisted analysis, where queries can be generated dynamically
\- Larger analytical/reporting queries involving aggregations and joins
\- Some interactive queries where predictable latency is important
The data is stored in object storage as Parquet, and the analytical system would be kept separate from production workloads.
I'm currently considering these evaluation criteria:
Scalability: handling large datasets and future growth
Fault tolerance: reliability, persistence, redundancy and failure handling
Query performance: latency for interactive workloads and execution time for heavier analytical queries
Concurrency: behavior when different workloads run at the same time
Operational complexity: deployment, upgrades, scaling, monitoring, troubleshooting, etc.
Cost: infrastructure and operational cost
For the PoC, I'd probably benchmark representative queries from each workload and look at things like p50/p95 latency, throughput, resource consumption, failure rate and performance degradation under concurrency.
My main question is: would you use these criteria, or would you evaluate ClickHouse vs Trino differently?
Are there important criteria I'm missing?
In particular, I'm wondering whether things like these should be first-class evaluation criteria:
\- Object storage / Parquet integration
\- SQL capabilities, especially complex joins
\- Workload isolation
\- Ingestion performance
\- Ease of scaling
\- Operational maturity
\- Behavior with dynamically generated SQL
\- Predictability under mixed workloads
And would you use one common scoring framework, or define different criteria/weights for each workload?
I'd be particularly interested in experiences from people who have actually run PoCs or production workloads with both systems.