| To: | Marko Myllynen <myllynen@xxxxxxxxxx>, Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Oracle connection debugging (was Re: Handling Oracle PMDA Latencies) |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 19 May 2016 22:39:49 +1000 |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <573D897A.5070804@xxxxxxxxxx> |
| References: | <56F25541.9020602@xxxxxxxxxx> <570F511E.5000605@xxxxxxxxxx> <1512930308.40394593.1460673441009.JavaMail.zimbra@xxxxxxxxxx> <57108708.3080906@xxxxxxxxxx> <571092DF.8050409@xxxxxxxxxx> <57175FC8.2000600@xxxxxxxxxx> <1558022602.42320984.1461208897951.JavaMail.zimbra@xxxxxxxxxx> <57395F04.2090909@xxxxxxxxxx> <1695396289.47966126.1463381940778.JavaMail.zimbra@xxxxxxxxxx> <573D897A.5070804@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 19/05/16 19:38, Marko Myllynen wrote: > ...Just a reminder, two-threaded PMDAs (one for PMCD, one for SQL) and PM_ERR_PMDANOTREADY were invented in the first place to accommodate slow DBMS PMDAs. |
| Previous by Date: | Fix pmrep infinity handling, Marko Myllynen |
|---|---|
| Next by Date: | Re: [pcp] per cpu utilisation from archive - pmval, Allan McAleavy |
| Previous by Thread: | Re: Oracle connection debugging (was Re: [pcp] Handling Oracle PMDA Latencies), Marko Myllynen |
| Next by Thread: | Re: [pcp] Oracle connection debugging (was Re: Handling Oracle PMDA Latencies), Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |