if you have a process that runs for multiple minutes, the measurements seem to "forget" the start.
E.g., here is an example where it starts at 251345ms.
"resources":
"cpu":
"energy used system": "0 J"
"used process":
"avg": !!int "0"
"max": !!int "250"
"min": !!int "0"
"timeseries":
"timestamps":
- "251345ms"
- "266408ms"
- "275043ms"
A good behaviour would be if it reports the measurements uniformly distributed over time.
if you have a process that runs for multiple minutes, the measurements seem to "forget" the start.
E.g., here is an example where it starts at 251345ms.
A good behaviour would be if it reports the measurements uniformly distributed over time.