The reductions is just the amount of times a function was called in a process, so it should always be climbing on long lived processes. 
OvermindDL1
0
Phillipp
But in my case, the tracking processes are started and later stopped. In the screenshot above, on the Processes graph, there you can see some spikes. That’s when tracking processes were started. But the Reductions increase all the time and the graph doesn’t show the total amount of recorded reductions but uses irate(). So the amount of active reductions also keeps increasing. It actually has very close similarities to the IO and Bytes Reclaimed graphs.
I wonder if it’s really just the metrics endpoint that fills up with more and more data (due to bots hitting 404 routes every now and then) and therefore creates load.
0