pcp
[Top] [All Lists]

Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue, 04 Nov 2014 10:10:34 +1100
Cc: 'Dave Brolley' <brolley@xxxxxxxxxx>, 'PCP Mailing List' <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20141103215816.GC3859@xxxxxxxxxx>
References: <542C21AE.1010504@xxxxxxxxxx> <007e01cfe010$7867f090$6937d1b0$@internode.on.net> <545110DC.2020104@xxxxxxxxxx> <y0mtx2hmwml.fsf@xxxxxxxx> <001d01cff6d7$0e9e4a50$2bdadef0$@internode.on.net> <20141103142643.GA3859@xxxxxxxxxx> <5457F82D.3050307@xxxxxxxxxxxxxxxx> <20141103215816.GC3859@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
G'day Frank.

On 04/11/14 08:58, Frank Ch. Eigler wrote:
...
I see what you mena, but unfortunately, the PAPI event code space (at
least 32 bits) is much larger than the PMID low-order bits space, is
not densely encoded, and bound to get worse when we address counters
with extra option flags, "uncore" counters, and per-process/-cgroup.

I was not advocating a fixed mapping ... while there may be more than 2^22 possible event counters, is it really the case that on one machine we could expect that more than 4 million different event codes to be enabled and exported by the PMDA?

The pmdaCache* routines would allow a dense allocation of more than 4 million unique ids and maintain a persistent mapping from the PMNS name that the PMDA chooses and those unique ids.

Perhaps someone could send me the output from:

        $ pminfo -dm papi

from a machine where the papi PMDA is running and collecting real data.

Then restart the PMDA, start a different collection profile and repeat the command above.

This might give me some concrete context to understand the issues if I've got it wrong.

<Prev in Thread] Current Thread [Next in Thread>