Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, I have the following problem, during my loads the Qlilview server gets slow on the network, running from the ping command 10.1. *. * It increases the response time considerably, can anyone help me?
Probably due to RAM exhaustion.
Connect to your server (by way of RDP), start task manager, select the Performance tab and watch it when the server starts to reload. What is the peak memory usage in %.
Hello, Memory usage is at 30%, the processing of the 90% peaks at that time the response time on the network gets very high
That means that your server has not enough RAM to run both QVS (with a number of documents loaded) and the reload tasks you have scheduled. Since the reloads are actually sort-of blackbox operations without user interface and no human waiting for them to finish in a certain amount of time, you will most likely experience the negative effects of this collision in QVS response times: the QlikView Access Point will become sluggish.
Note that every reload task is a separate process that will try to allocate its own RAM blocks. Fortunately at the end of the reload, RAM for a particular task will be released, so this 90% situation is not permanent.
There is one quick solution that won't cost you more than a bit of energy and time: reschedule all reloads to a window in which you don't expect your users to be on-line.
But there is only one real, long-term solution: buy and install more RAM.
Intermediate solutions include optimizing your documents (QVS uses less RAM) or streamlining your load scripts, but those come without any guarantees whatsoever to mitigate the 90% situation.
Best,
Peter
Hello Peter, my server has 192 RAM, I am not using nor 30% of its capacity, the problem occurs during the loads my processor reaches 90% sometimes with peak of 100%, at that time my server response time in Network gets high when I ping. 10. * 1. * 1. * it takes time to respond causing slowness.
Indeed, the situation you are descrbing is what I explained in my previous post. No I'm not a psychic; everybody who runs QlikView servers gets in this fight between QlikView Server and Distribution Service sooner or later.
In other words (and based on what information you provided in this thread, correct me if I'm making the wrong assumptions):
There you have it. The reloads won't crash. But they will take even more time to complete because of the swapping. And your QVS will become sluggish, if not completely unresponsive.
This unpredictable memory consumption is the main reason why in high-load environments a Publisher is usually run on a separate machine.