Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

sonikajain
New Contributor

how to determine the time taken for an object to get refreshed on UI

Hi all,

I am looking for a means to determine the time taken for objects to get refreshed on the UI after the selections are made.

Actually,we are working on the performace tuning of our app in terms of user response time, and wanted to compare how long the object/sheet took to refresh when the calcs are on the UI VS how long it takes when the calcs are shifted to the back.

Thanks,

Sonika Jain

3 Replies
Not applicable

Re: how to determine the time taken for an object to get refreshed on UI

Have you found your answer ?

Siva_Sankar
Honored Contributor

Re: Re: how to determine the time taken for an object to get refreshed on UI

Rob's Document Analyser and Doclog analyser serves for this purpose.

whiteline
Honored Contributor II

Re: how to determine the time taken for an object to get refreshed on UI

Hi.

There is build in profiler that shows that time: Sheet Properties->Objects->Time.

But there are some notes. As the calculation engine is multithreaded when there are more than one object these values are useless 'cause you don't know when one object starts and other ends. And there is no total time.

Also QlikView caches the result of calculations and you see zeros (even if you reopen the document).

So first you have to place the object to optimize on the separate sheet. Restart QV and check the Time for the object.

Then optimize it, restart and compare the results.

Then as the calculation is multithreaded you can repeat it for the entire sheet and see the result. Unfortunately for this case you don't have any metrics only your eyes.

The server makes calculations a little bit different (cause QV uses different in-memory structure depending on the size of free memory), so you can try and check the result of an optimization there but there is also no access to the metrics.