| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Process analysis |
| From: | Nicolas Michel <be.nicolas.michel@xxxxxxxxx> |
| Date: | Fri, 14 Nov 2014 17:02:47 +0100 |
| Cc: | Shirshendu Chakrabarti <shirshendu@xxxxxxx>, yves.weber@xxxxxx, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SKG0gYkXkrLuCoPUx3+HOr6lui52ylrA9UJhATHZBU8=; b=zd1wvnSkAYyjCuUy1lO82HKtYb8BGnWbq+uH0NSyQzjPfCSefgkULC9QyY1gYStyej ezqAOX7/T5CKAic74i7aXRshrX7LLcD3WgrNJgUPEhbctE1CjOcufXyNrm0dbDO2a5ez TFkmSUOVTnqvFhLlkoacAB4MZLXuVc9vg5QEnk08RXgDf8mnvMV85izKgNpnMOyyZr5S 9M3tg43h916u5N23VDsUrPqjdnZjBxRUlmu1Xne6sBziX61Jid+IF6hnBKRQFdzuOGCr ASuBq3i2LuXUyLw/f8unr7su0uin5YlWkrZGn5YDWOb6JVCsP1lSwuS4KEovd1W+QQBU AyIw== |
| In-reply-to: | <20141114152716.GI6430@xxxxxxxxxx> |
| References: | <CAO5znat7ceWKn8wf0RKC=GNzagqv3dsa=r-zfFTL4MxgLeue9w@xxxxxxxxxxxxxx> <y0mvbmjdoep.fsf@xxxxxxxx> <CALg+gg=UpskZYxGyiCavtzD5tn5TC3KwNu9UQF=7z+MLJMCarw@xxxxxxxxxxxxxx> <20141114152716.GI6430@xxxxxxxxxx> |
|
Thank you all for your ideas. We'll try the native web app ;) The majority of ideas you propose, if I understand well, makes possible to measure the stats of predefined processes we have to configure. It is great when you know in advance which process and what in the process you want to watch. Before, in case of a performance problem (a real case I had here), you first have to identify which process is the cause of the performance problem. So I would wanted something more like a top with history, and with I/O stats (it only keeps says the stats of the tenth hungrier processes). I think it would be a great plugin, disabled by default of course. And I would want to check process stats every hour or 2 hours (it is a matter of reading /proc/* I suppose?). In case of problem, we could change the precision or even seing it "live" like when connecting to pmcd directly with pmchart. I need more a by-process statistics than intra-kernel stats. That "magical" plugin ;) would able me to tell: it is the process XYZ with PID XXX that from 01:00pm to 02:00pm used the more the I/O, at a first glance. Then I would be able to watch that particular process more closely/precisely, with custom probes if necessary, which systemtap-pcp is for if I understood well. I know collected have a feature that can help: you can have a timeline of processes forking. But collected is not well packaged and difficult to install/configure (and often crash). And it doesn't give me I/O, memory and CPU stats by-process. 2014-11-14 16:27 GMT+01:00 Frank Ch. Eigler <fche@xxxxxxxxxx>: Hi - Nicolas MICHEL
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: test - please ignore, Troy McCorkell |
|---|---|
| Next by Date: | Re: [pcp] [RFC] pcp python patch, David Smith |
| Previous by Thread: | Re: [pcp] Process analysis, Frank Ch. Eigler |
| Next by Thread: | RE: [pcp] Process analysis, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |