Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
sudhakar_c
Partner - Contributor III
Partner - Contributor III

Performance - System Engine Logs

Hi,

As per the recommendation - network and persistence the network latency should be less than 4ms but in the system engine logs the message it is giving during peak hours is for example - "QrsSecurityManagement: Retrieved privileges in 384 ms from the QRS". Please refer screenshot. 

During this time users are using the application and reloading for the same application is also in progress.

We are using a Multi node setup and reload is happening on the RIM node. QRS DB is on the central node.

Does this message mean the network is too slow, so the system is performing very slow resulting in delayed reload or delayed dashboards loading? / How do we interpret this message in terms of performance? 

 

sudhakar_c_0-1635483739958.png

 

Labels (1)
1 Solution

Accepted Solutions
Sebastian_Linser

Hello @sudhakar_c 

This message means that it took an x amount of milliseconds to retrieve validations of current security rules request from the Engine towards the Repository Database via the Repository Service.

It does not say that the network  is slow. The latency 4ms would be measurable with e.g. ping. 

It means that the query in the back took a while to be processed and returned. 

If you have many custom security rules that could take longer. Check the performance of your central node during peaks that is on place where the bottleneck would show first. (E.g. cpu on more than 90% for more than 5 min)

Best Regards 

Sebastian 

Help users find answers! Don't forget to mark a solution that worked for you! 🙂

View solution in original post

1 Reply
Sebastian_Linser

Hello @sudhakar_c 

This message means that it took an x amount of milliseconds to retrieve validations of current security rules request from the Engine towards the Repository Database via the Repository Service.

It does not say that the network  is slow. The latency 4ms would be measurable with e.g. ping. 

It means that the query in the back took a while to be processed and returned. 

If you have many custom security rules that could take longer. Check the performance of your central node during peaks that is on place where the bottleneck would show first. (E.g. cpu on more than 90% for more than 5 min)

Best Regards 

Sebastian 

Help users find answers! Don't forget to mark a solution that worked for you! 🙂