| To: | Michele Baldessari <michele@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] hinv.* |
| From: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
| Date: | Thu, 23 Oct 2014 10:09:40 +1100 |
| Cc: | Nathan Scott <nathans@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <573592010.74725901.1413999659304.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <20141021222355.GC6656@xxxxxxxxxxxxxxx> <573592010.74725901.1413999659304.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 |
On 10/23/2014 04:40 AM, Nathan Scott wrote: Hi Michele, ----- Original Message -----Hi all, while for most hinv.* metrics I do not expect any changes over time (hinv.pagesize, hinv.ncpu, ...), I was a bit surprised that also hinv.cpu.clock seems to not change over time (F21 updated today, here). The original code was written before CPU clock throttling, cstates and so forth, and hence didn't expect the clock to change. It does nowdays! Attached patch should fix it (untested but should be fine). I'll also need to check if the default pmlogger config only logs hinv.cpu.clock once - that might need an update too, and of course some QA. Regards -- Mark
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] hinv.*, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] hinv.*, Michele Baldessari |
| Previous by Thread: | Re: [pcp] hinv.*, Nathan Scott |
| Next by Thread: | Re: [pcp] hinv.*, Michele Baldessari |
| Indexes: | [Date] [Thread] [Top] [All Lists] |