mirror of
https://github.com/zama-ai/concrete.git
synced 2026-02-09 03:55:04 -05:00
Previousely, we were sending parsed benchmark results to a Prometheus instance. Do to its time-series nature, Prometheus would downsample database content to avoid having to much data points for a given range of time. While this behavior is good for a continuous stream of data, like monitoring CPU load, it's not suited for benchmarks. Indeed benchmarks are discrete events that would occurr once in a while (i.e once a day). Downsampling would, at some point, simply omit some of benchmarks results. Using a regular SQL database like PostgreSQL solves this issue.