Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Join this live chat April 6, 10AM EST - QlikView to Qlik Sense REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
kris_vliegen
Partner
Partner

Reloads are loading too long

Hi All,

Last weekend we've upgraded our ServerSoftware from  QV 11 SR12 to QV11 SR17 because at some times we had memmory-problems. The memory went to 100% and the connection to the server via remote desktop and accesspont get lost.

After the upgrade the memory seems under control.

Only at some times the reloads are taking to much time.

Reloads of 7 sec are loading over 3 min.

We have a ot of reloads and if every reload is taking more time at a giving point in time there are to much reloads at the same time so all the reloads are giving an error (I've inserted for every reload a timeout).

Who can help me why this is happening?

Regards,

Kris

4 Replies
Peter_Cammaert

RAM exhaustion?

The QDS+QVB combo uses memory not allocated by the QVS. Because the QVS usually grabs more and more RAM over time, fewer bytes will be left to perform reloads in. The QDS is not that picky about available RAM, it will just start swapping to disk until it has enough memory to complete are reload. However, this may slow the reload down to a crawl.

Two solutions:

  • buy more RAM for your single server solution so that all services always have enough of it, or
  • put the publisher on its own machine so that no memory conflicts arise between the service that does the reloads and the service that does the displaying of QlikView documents.

Best,

Peter

kris_vliegen
Partner
Partner
Author

Hi Peter,

thaks for the quick response.

But if the reloads are failing we only have 20% of our memeory in use.

And 45 % of CPU.

We have 128Gb memory in our machine

Peter_Cammaert

The failures are self-generated, you were saying? The problem with reloads failing is that there is no residual load on either CPU or RAM. Because when a QVB job is aborted, all memory is released back to the free RAM pool.

Did you monitor your server load while tasks were starting to slow down and until the first few failures were triggered?

kris_vliegen
Partner
Partner
Author

I have 1 reload of a large qvd's and a large dashboard

The biggest qvd's are 2.1 GB  and 0.5 GB (3-times).

And the dashboard is about 1,2 GB.

This runs every 2 hours.

It looks that if he is creating those qvd's and the dashboard he is getting a hard time.

But for a server with 128 GB of RAM it couldn't be a problem (or am I wrong?)

And why didn't we have this problem before the upgrade?

Sometimes we ran out of memory, but the reloads were reacting normal.

regards,

Kris