5c2f9e7f71
Currently, when a reprocessing task is scheduled, CloudKitty executes the cleaning of the data for the reprocessing period in one hour fashion (the default period). Therefore, for each one of the timeframes, a delete query is sent to InfluxDB (when using it as a backend). However, InfluxDB is not a very optimized time series database for deletion; thus, this workflow generates quite some overhead and slowness when reprocessing. If we clean right away the whole time frame for the reprocessing task, and then we just reprocess it, it will execute a single delete query in InfluxDB, which has a similar cost as a delete to remove the data for a single time frame. This patch optimized the reprocessing workflow to execute batch cleaning of data in the storage backend of CloudKitty. Change-Id: I8282f44ad837c71df0cb6c73776eafc7014ebedf
6 lines
136 B
YAML
6 lines
136 B
YAML
---
|
|
features:
|
|
- |
|
|
Optimized the reprocessing workflow to execute batch cleaning
|
|
of data in the storage backend of CloudKitty.
|