| To: | PCP <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates: dynamic container switching prototype |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 15 Oct 2015 01:38:39 -0400 (EDT) |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <2041445273.54854877.1444886622259.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <2041445273.54854877.1444886622259.JavaMail.zimbra@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | PtUjKLfvtDqwrFS7ziTmVuUh1oBnVS/u8F5d |
| Thread-topic: | pcp updates: dynamic container switching prototype |
Hi all, This is the prototype code referenced here, of course: http://pcp.io/pipermail/pcp/2015-October/008486.html ----- Original Message ----- > Changes committed to git://git.pcp.io/nathans/pcp.git master > > Nathan Scott (1): > pmcd: implement dynamic switching of monitored containers > One thing I forgot to mention in the commit message was that this code includes a change to pmdapmcd to simplify handling of the "pmcd.client.whoami" metric. Instead of a separate table, with independent grow/slot-reuse rules, that is rolled into the other (per-context) table where the container, and other per-context state already lived. I believe the separate table existed because that metric predated pmdaprocs per-client-context support, hence this simplification of the pmdapmcd code is a nice little side-effect. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: dynamic container switching prototype, Nathan Scott |
|---|---|
| Next by Date: | pcp updates: pmlogger semantics change, 1st round of strtoint64 changes, Ken McDonell |
| Previous by Thread: | pcp updates: dynamic container switching prototype, Nathan Scott |
| Next by Thread: | pcp updates: pmlogger semantics change, 1st round of strtoint64 changes, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |