| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Mon, 3 Nov 2014 09:26:43 -0500 |
| Cc: | "'Dave Brolley'" <brolley@xxxxxxxxxx>, "'PCP Mailing List'" <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <001d01cff6d7$0e9e4a50$2bdadef0$@internode.on.net> |
| References: | <542C21AE.1010504@xxxxxxxxxx> <007e01cfe010$7867f090$6937d1b0$@internode.on.net> <545110DC.2020104@xxxxxxxxxx> <y0mtx2hmwml.fsf@xxxxxxxx> <001d01cff6d7$0e9e4a50$2bdadef0$@internode.on.net> |
| User-agent: | Mutt/1.4.2.2i |
Hi, Ken - > [...] by "metadata differences" I mean a metric that appears in more > than one archive and has some difference in the pmDesc data that > describes that metric or the associated PMNS fragment that maps a > name to a PMID ... this means - name [...] One glitch with that could be PMDAs whose PMNS is dynamic from run to run (like the papi pmda, which is almost able to be used as a logged data source). The name-to-PMID mapping may vary there (as new PAPI versions come, or host CPU changes, new counters(=metrics) may appear in some odd sequence, so get scrambled PMIDs), but the name & pmDesc (semantics etc.) would remain the same and previous values comparable. I don't know how pervasive this situation would be, but if it's not too hard to support, we should. (e.g., we could track metrics across archives by name rather than pmid.) - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools, Dave Brolley |
|---|---|
| Next by Date: | RFC: papi pmda auto-enable on fetch, Frank Ch. Eigler |
| Previous by Thread: | Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools, Dave Brolley |
| Next by Thread: | Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |