Alex Petrov
Alex Petrov
As @mpenet noted, we need to use prepared statements rather than the usual ones.
Currently, we're supporting only `?` and `*`. We can add support for `{}` by expanding to multiple series.
Since we always fetch the data knowing resolution and path (`id` column), we can avoid fetching it from the database (also because it's being fetched N time instead for N...
Currently, if one wants to migrate, they're on their own. I suggest we create a tool that helps to migrate any graphite installation to cyanite with ease.
It'd be great if we could avoid round-trips to Cassandra index for every dashboard query we do. Thing is that when we're doing wildcard queries to dashboard, we keep hitting...
I've made a trivial port of one of our functions (I have to say it doesn't have the date normalisation), which could be used as grounds for the further discussions...
Right now, we'll grow partitions indefinitely. We need to include some sort of `timestamp mod partition resolution` function and run functions against averaged partitions instead to improve performance and reduce...
It could be beneficial for memory to store the md5 hash of metric instead of the metric name in memory. Currently, we keep the metric names in memory for the...
Hi, It seems that it's very possible to avoid using Temporal and Temporal function (actually, it's done quite similarly in Erlang implementation). I believe that what they do technically belongs...