Hello everyone,We have made the installation of version 10.7 but we are with CPU consumption problems that prove that from time to time the Webview freezes and does not show alarms or metrics. It has been detected that the process that produces this is the Async MDQ, someone will know how to configure or in any case deactivate it.
Are you using webview and the em on the same server? What heap settings did you allocate for both and how much RAM is on the server?
The MOM and the Webview are in distinct server.
The MOM have 14 GB of 16 GB RAM.
The Webview have 12 GB of 16 GB RAM
Further to Matt's suggestions, when the data access problem occurs with WebView does it also occur with the Workstation? If yes then the root cause may be the MOM performance rather than WebView and the perflog.txt might be worth looking at: How to interpret the values of Perflog.txt fields. - CA Knowledge
Yes la Webview and the Workstation is affected.
Reviewing the performance of the MOM we realized that the Async MDQ process is the one that consumes many resources affecting its operation. This is why we want to configure or modify it.
Hi Martin,The Async MDQ threads handle all asynchronous queries for WebView, Workstation and CLW.Therefore high CPU for Async MDQ threads indicates problem is probably related to metric queries i.e. the number of queries and volume of data being requested. So you can first examine the queries that are being executed.
There are property clamps that can protect to some degree the amount of data that a query can return :introscope.enterprisemanager.query.datapointlimitintroscope.enterprisemanager.query.returneddatapointlimitThey are described herehttps://docops.ca.com/ca-apm/10-5/en/administrating/properties-files-reference/introscopeenterprisemanager-properties#IntroscopeEnterpriseManager.properties-EnterpriseManagerMetricClamping
Hope it helps.
Both properties are hidden so need to be explicitly added to the IntroscopeEnterpriseManager.properties file for all Collectors.
They default to 0 = unlimited and changes are subject to Hot config so do not need an EM restart.
From what I understand the properties only apply to Top-N and CLW queries.
Thank you for your help.