topic Re: Best practices for perfomance tunning frontend? in QlikView

Frontend performance tunning on access point ,best practices.

swarup_malli — Mon, 26 Jan 2026 18:19:17 GMT

Hi,

Lately one of our dashboards has been very slow in responding.

I tried to fix it by doing the following:

1) Allocating more RAM on the QV server

2) Allocating more CPU power

Unfortunately response time hasn't improved much, its still very slow. Even though the RAM and CPU usage is not even 50% .

On further investigation ,found

1) Lately the app has been dealing with more data ( since it was deployed) i.e. more records.

2) There are certain charts and tables that are taking a while to load ,because they are try to display all the data.

3) I feel a lot of network bandwidth is being utilized because of this.

Did the following testing on my desktop:

1) Reload speed is acceptable .

2) The response time is fast ( problem starts when user tries to access it on access point ,the response is slower than molasses going uphill in arctic winter conditions )

Would the following workarounds work:

1) Move the calculations done by the expressions in the chart to the backend ( script editor)

2) Limit the number of rows displayed by the chart

3) By using a condition in the chart were the user is forced to make a selection to see corresponding data on the chart, till then chart doesn't display anything.

As many QV developers must have faced these kind of scenarios at some point ,I was hoping to get some pointers from you guys to performance tune my dashboards.

Thanks

Swarup

Re: Tips on making dashboard response time faster on access point

Marcio_Campestrini — Wed, 12 Nov 2014 18:38:58 GMT

Hi Swarup

I use the third workaround (force user to make selections to see the data.

Márcio

Re: Best practices for perfomance tunning frontend?

Anonymous — Wed, 12 Nov 2014 19:48:59 GMT

I find the Document Document Analyzer V2 -- a major update of Rob Wunderlich very useful.

Document Analyzer V2 -- a major update

Re: Frontend performance tunning,best practices.

swarup_malli — Thu, 13 Nov 2014 14:34:02 GMT

Just found out the IE browser 10 for responsible for slow response by the dashboards,the problem disappeared when I switched to Forefox.

never realized browser could slow down the response, strange but true

Re: Frontend performance tunning,best practices.

Marcio_Campestrini — Thu, 13 Nov 2014 15:23:56 GMT

Swarup,

I defined Google Chrome in my environment. It showed itself more stable.

Re: Frontend performance tunning,best practices.

swarup_malli — Thu, 13 Nov 2014 15:25:24 GMT

Thank you for input guys !