ClickHouse vs M3
A detailed comparison
Compare ClickHouse and M3 for time series and OLAP workloads
Learn About Time Series DatabasesChoosing the right database is a critical choice when building any software application. All databases have different strengths and weaknesses when it comes to performance, so deciding which database has the most benefits and the most minor downsides for your specific use case and data model is an important decision. Below you will find an overview of the key concepts, architecture, features, use cases, and pricing models of ClickHouse and M3 so you can quickly see how they compare against each other.
The primary purpose of this article is to compare how ClickHouse and M3 perform for workloads involving time series data, not for all possible use cases. Time series data typically presents a unique challenge in terms of database performance. This is due to the high volume of data being written and the query patterns to access that data. This article doesn’t intend to make the case for which database is better; it simply provides an overview of each database so you can make an informed decision.
ClickHouse vs M3 Breakdown
 |
 |
|
| Database Model | Columnar database |
Time series database |
| Architecture | ClickHouse can be deployed on-premises, in the cloud, or as a managed service. |
The M3 stack can be deployed on-premises or in the cloud, using containerization technologies like Kubernetes or as a managed service on platforms like AWS or GCP |
| License | Apache 2.0 |
Apache 2.0 |
| Use Cases | Real-time analytics, big data processing, event logging, monitoring, IoT, data warehousing |
Monitoring, observability, IoT, Real-time analytics, large-scale metrics processing |
| Scalability | Horizontally scalable, supports distributed query processing and parallel execution |
Horizontally scalable, designed for high availability and large-scale deployments |
Looking for the most efficient way to get started?
Whether you are looking for cost savings, lower management overhead, or open source, InfluxDB can help.
ClickHouse Overview
ClickHouse is an open source columnar database management system designed for high-performance online analytical processing (OLAP) tasks. It was developed by Yandex, a leading Russian technology company. ClickHouse is known for its ability to process large volumes of data in real-time, providing fast query performance and real-time analytics. Its columnar storage architecture enables efficient data compression and faster query execution, making it suitable for large-scale data analytics and business intelligence applications.
M3 Overview
M3 is a distributed time series database written entirely in Go. It is designed to collect a high volume of monitoring time series data, distribute storage in a horizontally scalable manner, and efficiently leverage hardware resources. M3 was initially developed by Uber as a scalable remote storage backend for Prometheus and Graphite and later open-sourced for broader use.
ClickHouse for Time Series Data
ClickHouse can be used for storing and analyzing time series data effectively, although it is not explicitly optimized for working with time series data. While ClickHouse can query time series data very quickly once ingested, it tends to struggle with very high write scenarios where data needs to be ingested in smaller batches so it can be analyzed in real time.
M3 for Time Series Data
M3 is specifically designed for time-series data. It is a distributed and scalable time-series database optimized for handling large volumes of high-resolution data points, making it an ideal solution for storing, querying, and analyzing time-series data.
M3’s architecture focuses on providing fast and efficient querying capabilities, as well as high ingestion rates, which are essential for working with time-series data. Its horizontal scalability and high availability ensure that it can handle the demands of large-scale deployments and maintain performance as data volumes grow.
ClickHouse Key Concepts
- Columnar storage: ClickHouse stores data in a columnar format, which means that data for each column is stored separately. This enables efficient compression and faster query execution, as only the required columns are read during query execution.
- Distributed processing: ClickHouse supports distributed processing, allowing queries to be executed across multiple nodes in a cluster, improving query performance and scalability.
- Data replication: ClickHouse provides data replication, ensuring data availability and fault tolerance in case of hardware failures or node outages.
- Materialized Views: ClickHouse supports materialized views, which are precomputed query results stored as tables. Materialized views can significantly improve query performance, as they allow for faster data retrieval by avoiding the need to recompute the results for each query.
M3 Key Concepts
- Time Series Compression: M3 has the ability to compress time series data, resulting in significant memory and disk savings. It uses two compression algorithms, M3TSZ and protobuf encoding, to achieve efficient data compression.
- Sharding: M3 uses virtual shards that are assigned to physical nodes. Timeseries keys are hashed to a fixed set of virtual shards, making horizontal scaling and node management seamless.
- Consistency Levels: M3 provides variable consistency levels for read and write operations, as well as cluster connection operations. Write consistency levels include One (success of a single node), Majority (success of the majority of nodes), and All (success of all nodes). Read consistency level is One, which corresponds to reading from a single nod
ClickHouse Architecture
ClickHouse’s architecture is designed to support high-performance analytics on large datasets. ClickHouse stores data in a columnar format. This enables efficient data compression and faster query execution, as only the required columns are read during query execution. ClickHouse also supports distributed processing, which allows for queries to be executed across multiple nodes in a cluster. ClickHouse uses the MergeTree storage engine as its primary table engine. MergeTree is designed for high-performance OLAP tasks and supports data replication, data partitioning, and indexing.
M3 Architecture
M3 is designed to be horizontally scalable and handle high data throughput. It uses fileset files as the primary unit of long-term storage, storing compressed streams of time series values. These files are flushed to disk after a block time window becomes unreachable. M3 has a commit log, equivalent to the commit log or write-ahead-log in other databases, which ensures data integrity. Client Peer streaming is responsible for fetching blocks from peers for bootstrapping purposes. M3 also implements caching policies to optimize efficient reads by determining which flushed blocks are kept in memory.
Free Time-Series Database Guide
Get a comprehensive review of alternatives and critical requirements for selecting yours.
ClickHouse Features
Real-time analytics
ClickHouse is designed for real-time analytics and can process large volumes of data with low latency, providing fast query performance and real-time insights.
Data compression
ClickHouse’s columnar storage format enables efficient data compression, reducing storage requirements and improving query performance.
Materialized views
ClickHouse supports materialized views, which can significantly improve query performance by precomputing and storing query results as tables.
M3 Features
Commit Log
M3 uses a commit log to ensure data integrity, providing durability for write operations.
Peer Streaming
M3’s client peer streaming fetches data blocks from peers for bootstrapping purposes, optimizing data retrieval and distribution.
Caching Mechanisms
M3 implements various caching policies to efficiently manage memory usage, keeping frequently accessed data blocks in memory for faster reads.
ClickHouse Use Cases
Large-scale data analytics
ClickHouse’s high-performance query engine and columnar storage format make it suitable for large-scale data analytics and business intelligence applications.
Real-time reporting
ClickHouse’s real-time analytics capabilities enable organizations to generate real-time reports and dashboards, providing up-to-date insights for decision-making.
Log and event data analysis
ClickHouse’s ability to process large volumes of data in real-time makes it a suitable choice for log and event data analysis, such as analyzing web server logs or application events.
M3 Use Cases
Monitoring and Observability
M3 is particularly suitable for large-scale monitoring and observability tasks, as it can store and manage massive volumes of time-series data generated by infrastructure, applications, and microservices. Organizations can use M3 to analyze, visualize, and detect anomalies in the metrics collected from various sources, enabling them to identify potential issues and optimize their systems.
IoT and Sensor Data
M3 can be used to store and process the vast amounts of time-series data generated by IoT devices and sensors. By handling data from millions of devices and sensors, M3 can provide organizations with valuable insights into the performance, usage patterns, and potential issues of their connected devices. This information can be used for optimization, predictive maintenance, and improving the overall efficiency of IoT systems.
Financial Data Analysis
Financial organizations can use M3 to store and analyze time-series data related to stocks, bonds, commodities, and other financial instruments. By providing fast and efficient querying capabilities, M3 can help analysts and traders make more informed decisions based on historical trends, current market conditions, and potential future developments.
ClickHouse Pricing Model
ClickHouse is an open source database and can be deployed on your own hardware. The developers of ClickHouse have also recently created ClickHouse Cloud which is a managed service for deploying ClickHouse.
M3 Pricing Model
M3 is an open source database and can be used freely, although you will have to account for the cost of managing your infrastructure and the hardware used to run M3. Chronosphere is the co-maintainer of M3 along with Uber and also offers a hosted observability that uses M3 as the backend storage layer.
Get started with InfluxDB for free
InfluxDB Cloud is the fastest way to start storing and analyzing your time series data.
