| To: | PCP <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | Slow pmdapapi fetching |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 22 Jan 2015 20:29:52 -0500 (EST) |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <258293690.15607144.1421974332709.JavaMail.zimbra@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | pq1+XcRNeFhIgJ8/hM/RaF9zdPFhxA== |
| Thread-topic: | Slow pmdapapi fetching |
Hi all, I noticed pmdapapi timed out for me on fetch (the old pmcd terminating connection to slow-responding PMDA after 5secs chestnut) and after a little digging and chatting to Lukas it was found that sometimes it takes a very long time for auto-enable-everything mode to fire up... $ time sudo pminfo -v papi > /dev/null real 0m5.316s user 0m0.006s sys 0m0.018s and then subsequently, too ... $ time sudo pminfo -v papi > /dev/null real 0m1.765s user 0m0.012s sys 0m0.013s This is on my laptop (four CPUs), Lukas sees slightly better numbers locally; but always quite slow when compared to other PMDAs. The elapsed vs CPU utilised numbers suggest there's plenty of room for improvement, somewhere (maybe below PAPI interfaces though?). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: pcp2graphite, kenj qa, RHBZ 1180109, Dave Brolley |
|---|---|
| Next by Date: | pcp updates, pmmgr pid-file writing relaxation, Frank Ch. Eigler |
| Previous by Thread: | pcp updates: pcp2graphite, kenj qa, RHBZ 1180109, Dave Brolley |
| Next by Thread: | Re: Slow pmdapapi fetching, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |