3 ms·
In-kernel resource-specific counters are great, but those are limited to 10/60/300 seconds averages. For historic resource utilization, sar/sadc tool is still
by kees99 7y ago
In-kernel resource-specific counters are great, but those are limited to 10/60/300 seconds averages.
For historic resource utilization, sar/sadc tool is still a go-to.
- shuss 7y agokees99, you should check the "total" fields. They have information in microsecond resolution.
- kccqzy 7y agoIf I have a cron job and reads the pressure file and simply stores its contents with a time stamp for later analysis, would that be enough to determine historic resource utilization?
- shuss 7y agoWhile already available tools should have sufficed and PSI should be good for it, a very important capability that PSI provides system administrators is its high-resolution. Using PSI, with specialized tooling, system administrators can automate sensitive workload scheduling. I'm sure someone is already working on integrating information made available in PSI to Kubernetes so that the automation bit is taken care of.
- danw1979 7y agowhy not dump it into a time series database - even something as simple as a set of whisper files on a local disk can be a lot more useful than a flat file. go-carbon is my tool of choice for this kind of job.