M3 vs RRDtool

Choosing 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 M3 and RRDtool so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how M3 and RRDtool 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.

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.

RRDtool Overview

RRDtool, short for Round-Robin Database Tool, is an open-source, high-performance data logging and graphing system designed to handle time series data. Created by Tobias Oetiker in 1999, RRDtool is specifically built for storing and visualizing time-series data, such as network bandwidth, temperatures, or CPU load. Its primary feature is the efficient storage of data points, using a fixed-size database that automatically aggregates and archives older data points, ensuring that the database size remains constant over 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.

RRDtool for Time Series Data

RRDtool was created for time series data storage and visualization, making it a great fit for applications that require efficient handling of this type of data. Its round-robin database structure ensures constant storage space usage while providing automatic data aggregation and archiving. However, RRDtool may not be suitable for applications that require complex queries or relational data storage, as its focus is primarily on time series data.

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

RRDtool Key Concepts

• Round-robin database: A fixed-size database that stores time-series data using a circular buffer, overwriting older data as new data is added.
• RRD file: A single file that contains all the configuration and data for an RRDtool database.
• Consolidation function: A function that aggregates multiple data points into a single data point, such as AVERAGE, MIN, MAX, or LAST.

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.

RRDtool Architecture

RRDtool is a specialized time series database that does not use SQL or a traditional relational data model. Instead, it employs a round-robin database structure, with data points stored in a fixed-size, circular buffer. RRDtool is a command-line tool that can be used to create and update RRD files, as well as generate graphs and reports from the stored data. It can be integrated with various scripting languages, such as Perl, Python, and Ruby, through available bindings.