Score:1

What defines the "interval" when playing back Performance Co-Pilot data in pcp-atop?

in flag

I have PCP (Performance Co-Pilot) recording performance metrics on a RHEL 7 host. The recording cadence is set to Y seconds here:

/etc/pcp/pmlogger/control.d/local

When I copy the performance metrics logs to another machine I'm able to analyze the files using:

pcp atop --interval=Zs -r /path/to/archive/files/

(where Z is a value that may or may not be the same as Y)

When I jump around in the archive using the t and T commands I move by Z seconds, which makes sense.

My question is about the calculated values that pcp atop displays. According to man pcp-atop, values such as CPU utilization percentage and system memory utilization percentage are calculated over the past "interval", but it's unclear whether that interval is the capture interval or the display interval for replayed data.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.