| To: | Jeff Hanson <jhanson@xxxxxxx> |
|---|---|
| Subject: | Re: pmclusterd versus other solutions |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Thu, 01 Sep 2016 11:44:39 -0400 |
| Cc: | Mark Goodwin <mgoodwin@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <49c5d203-5378-5cbb-7092-7ed23035af56@xxxxxxx> (Jeff Hanson's message of "Thu, 1 Sep 2016 07:33:15 -0400") |
| References: | <3b551b84-ff74-5b9c-5854-3bdcba1c1212@xxxxxxx> <CAFmffyUkbMi1g3XScEE-XjEHBmdbd5WvHZ6UpGKN_eZtG6pm=g@xxxxxxxxxxxxxx> <49c5d203-5378-5cbb-7092-7ed23035af56@xxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
jhanson wrote: > [...] And regardless of the issues here I was interested in what > other people do with pcp to monitor cluster nodes. [...] That's a good question. PCP's one-host/archive-at-a-time mentality percolates, with only a few tools allowing limited co-mingling of data for a small number of machines. Our archive files, while well tuned for efficient initial logging from an individual host, are an obstacle to joint or ad-hoc analysis across time spans or hosts. The multi-archive work is a step forward, but there is a long way to go. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pmclusterd versus other solutions, Jeff Hanson |
|---|---|
| Next by Date: | [performancecopilot/pcp] Fix graphite API examples and a minor typo in pmwebapi manpage (#111), Mark Riedesel |
| Previous by Thread: | Re: [pcp] pmclusterd versus other solutions, Jeff Hanson |
| Next by Thread: | Re: [pcp] pmclusterd versus other solutions, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |