Distributable time-series database

Michael Leinartas 27c61997a9 Merge pull request #35 from mleinart/test_pypy 3 years ago
bin 0108f41dbc flake8 style fixes in bin/, update versions 4 years ago
docs 63fad63486 Document CeresNode and update doc styles 4 years ago
tests ed86b6e8ea Enable read tests after fixes applied 4 years ago
.gitignore 22278ffc0c Add sphinx docstring processing 6 years ago
.travis.yml cee80a5035 Trigger migrate to new travis ci infrastructure 3 years ago
LICENSE 5e8c9f08c1 Add license info 6 years ago
README.md 5e2a76531e Fix broken link in README 5 years ago
ceres.py 45fea85a63 Respect previous slice's boundaries 4 years ago
setup.py d9bb2e1769 Updating the ceres homepage url from lp to github 6 years ago
test_requirements.txt a5ea4d6df4 Use unittest2 on python2.6 4 years ago

README.md

Ceres

Build Status

Ceres is a component of Graphite as one of the time-series storage options available for use. Ceres provides a file format for incoming metrics to be persisted when received from the network. See also Whisper

Overview

Ceres is a time-series database format intended to replace Whisper as the default storage format for Graphite. In contrast with Whisper, Ceres is not a fixed-size database and is designed to better support sparse data of arbitrary fixed-size resolutions. This allows Graphite to distribute individual time-series across multiple servers or mounts.

Expected features such as roll-up aggregation and data expiration are not provided by Ceres itself, but instead are implemented as maintenance plugins in Carbon.