Highlighted
Contributor.. Contributor..
Contributor..
84 views

Priority and persistency impact on system performance

When creating TQL queries in UCMDB, you can choose if it should be persistent or not (remain in memory permanently) as well as choose the priority level (how often the TQL query is rerun automatically).

 

What is the impact on system performance when choosing a TQL query to be Persistent and High or Express Priority?

How many TQL queries can remain in memory permanently without impacting system performance?

Is there any way I can monitor the impact in the longer run, to know when I should change a TQL Query to not be persistent and lower the priority?

 

Regards

Jacob

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.