[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: High CPU consumption after client update (11.7.4) connected with a database/appserver (

Status
Not open for further replies.
D

dbeavon

Guest
What type of clients are upgraded to 11.7.4? OpenClients? .Net/Java? Can you capture the activity using 4GLTrace, and then replay it in a preproduction environment (using both the configurations)? It would be helpful if your observations could be verified on another server. It certainly seems odd that you would have such a high amount of CPU associated with the particular version of the remote openclient. However the openclients are fairly sophisticated nowadays and can connect to both PASOE and classic. Maybe there is some additional negotiation work that is happening in the legacy 10.2B agents. You should probably enable a variety of logging types and try to see if you can correlate CPU and the logs (long delays in the logging with high CPU). You should be able to modify your logging configuration on-the-fly in "classic" with the setting: allowRuntimeUpdates=1. It is probably not worth saying it anymore, but I would have suggested upgrading the server side of things first. Our OE server products are typically running more recent versions of OE than the clients (unless we have a client-specific hotfix). For example we run 11.7.5 for our database server (and appservers), but some of our SQL92 drivers are still using the 10.2.B library. It is easier to manage the centralized server products, and so they typically get attended to first. After that we try to "herd" the various types of remote clients. If I had to guess, you may be describing a configuration of the products which even Progress has never tested explicitly Did you try any of this in pre-production? Was there enough pre-production activity to compare the CPU behavior before/after? Did you also get around to upgrading the *server* side of things yet in pre-production? Are you comfortable pushing ahead with the upgrade on the *server* side of things, without first getting to the bottom of this particular performance mystery? At least the "only" problem you have is performance related ... it could have been worse. Once the server side of things is running a consistent version of OE, it won't be such an unusual configuration. At that point your tech support case may go more smoothly (if you still have a case).

Continue reading...
 
Status
Not open for further replies.
Top