News for hackers. Stuff that matters.
Re:Linux Pressure Stall Information (PSI) by Example by kees99 on Friday August 30, 2019 @07:00AM (#20837432)
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.

Re:Linux Pressure Stall Information (PSI) by Example by shuss on Friday August 30, 2019 @07:05AM (#20837453)
kees99, you should check the "total" fields. They have information in microsecond resolution.
Re:Linux Pressure Stall Information (PSI) by Example by kccqzy on Saturday August 31, 2019 @10:05AM (#20846320)
If 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?
Re:Linux Pressure Stall Information (PSI) by Example by shuss on Saturday August 31, 2019 @11:28AM (#20846830)
While 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.

Re:Linux Pressure Stall Information (PSI) by Example by danw1979 on Saturday August 31, 2019 @04:13PM (#20848551)
why 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.