pcp
[Top] [All Lists]

Re: [pcp] Compressing .meta file also?

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] Compressing .meta file also?
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Fri, 13 May 2016 11:07:54 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1478926031.47431716.1463099651741.JavaMail.zimbra@xxxxxxxxxx>
References: <1478926031.47431716.1463099651741.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0
On 05/13/2016 10:34 AM, Nathan Scott wrote:
Hi Ken,

I've seen two cases this week of people starting to get sufficiently
large archive .meta files that compression has been requested, or at
least considered (both times from the well known proc-indom issue).

The proc-indom issue is in large part due to the external instance names
for proc metrics - these include the pid and command *and* all arguments.
e.g. to see what I mean: run pminfo -f proc.psinfo.stime | grep chrome

I propose we shorten this to just the pid and cmd name, without all the args
- apps can also fetch proc.psinfo.psargs  if they need the entire command line.

Not sure how we'd accommodate downrev/remote clients, but it'd certainly
help reduce the metadata size in archives containing proc metrics.

-- Mark


As a stop-gap, is there any reason we'd not be able to auto-compress/
auto-expand the .meta files as well?  Not a long-term fix but has the
nice quality of being relatively backward-compatible ("just" a libpcp
change to add support, and some pmlogger_daily shell code I guess).

thanks.

--
Nathan

_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp


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