Saving policies takes time and hangs consoles OVPMAD performance
I am looking if there are maintenance jobs that can be used to help improve the performance of ovpmad. Currently if we save poliices it can take upto 5 mins to save a single policy. This also locks up the console from being able to do any other policy work
Any advice that can be provided to help us improve the performance of ovpmad would be greatly appreciated.
The issue is even worse on remote MMC consoles.
I would suggest to you that please trying to install the latest console patch OMW_00201, this will help to improve the performance of the console.
This has to be mroe than just a console issue. I see it as ovpmad performance issue or database indexing issue. I know there used to be tools that helped cleanup the database etc. and I am looking to see if any of that exists in OMW today.
There is no document or tips to improve OVPMAD performace perse. What you can find is a set of documents/tips that will help with the overall performance of the application, example:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
No real help but thanks, not sure how acknowledged messages can effect how long it takes for a policy to be saved. Someone has to have seen this issue and found a proper solution.
Do you see the performance issue with all policies? I have seen it take a long time to save the
policy when the policy is very large (i.e. has lots of rules) and in this case it would be expected to take some time.
So if you save a policy with only one single rule (lile a opcmsg policy) does it also take a long time?
If you find this or any post resolves your issue, please make sure to mark it as an "Accepted Solution".
If you liked the reply then please show this with KUDOs.
I am still looking for a solution or advice on this issue. It seems where we have more policies in a specific type like measurement threshold ones it takes the longest. Logfile or Scheduled action policies still take longer than I would expect but are faster. This is a real issues when 3 engineers are all trying to update policies at one time. We really need s fix for this problem.