Reload taking too long

[inescastelhano]

Hey folks!

I'm facing a real problem.

My Qlikview document uses incremental load; in the first run it usually takes 3-4 minutes, and after the that (qvds already generated), the document usually takes 30 sec-2 min (maximum) to execute offline (I mean, if I open it and manually execute it). Once I put the document on the server, the run time varies from 1-2 minutes to some hours! There is no reason for this to happen, and it has never happened before. We have already restarted the server, it seemed to get better on first run but now it seems to be the same. I have absolutely no idea of what could cause this. Any help is much appreciated.

Cheers,

Inês

[inescastelhano]

I see... Here it is.

[#3]

That's the one. Interesting!!! Not the Engine allocation as I suspected.

6/15/2016 04:43:24.9909095	Information	Task Dependencies are OK
6/15/2016 05:17:46.9770916	Information	Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

For some reason absolutely nothing happens between these two lines. Completely stalled for over 30 minutes. I'll do some investigation and come back to you.

You are running a rather old version of QlikView right? 11.0.11440.0?

[Anonymous]

Hi Inês,

See this two lines:

6/15/2016 04:43:24.9909095    Information    Task Dependencies are OK

6/15/2016 05:17:46.9770916    Information    Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

The difference of time is because QlikView Publisher, or QlikView Server, is allocating Engines to reload the document. While there aren't resources to do it, it still waiting.

Regards!

[inescastelhano]

Thanks ! I'll wait for your feedback. This is related to low machine resources, right?

The machine where QlikView is running is from our client, so yes, it's a rather old version...

Cheers,

Inês

[inescastelhano]

Machine resources, you mean?

[#7]

Machine resources is for sure something you should check.

I noticed there is massive stall at the very end of the task log.

6/15/2016 05:20:57.6098696	Information	Notifying all triggers of new state:Finished - completed
6/15/2016 06:16:36.2178682	Information	Saving Task Result

Other thing worth checking if there are any issues with Windows Performance Counters on this machine. Cause one thing that is done between the log lines are that we update task related Perfomance Counters.

[#8]

Manuel,

I don't think so. The allocation of the Engine happens between these log lines:

6/15/2016 05:17:46.9770916	Information	Allocating new QlikView Engine. Current usage count=2 of 15 (of type non-reader).
6/15/2016 05:17:46.9770916	Information	Max retries:5
6/15/2016 05:17:46.9770916	Information	Attempt:01
6/15/2016 05:17:47.9754852	Information	Allocated QlikView Engine successfully. Current usage count=3 of 15 (of type non-reader). Ticket number=178.

[Anonymous]

Sorry, I would say processors and rerources, not QlikView Engines.

[nizamsha]

i just want to confirm are you loading the same app in the same machine  where server machine is located if not

check the ram size in the server might be one of the reason if ram size is low then it will take some when compare to desktop reload or

check do u have enough space in your drive i hope  these are the reason for increasing ur load time on the server

[inescastelhano]

Yes to all your assumptions.