QlikView App Dev

[khasimvali85]

Hi,

Can Anybody Explain Memory Utilization in QV Server, Memory is Reached Maximum Size.

How can we Reasolve This?

Thanks

Khasim.

[ashfaq_haseeb]

Hi

Khasim It happens usually.

I must say it depend on the type of calculation you have in your application.

Nevertheless try by restarting QlikViewservices and will kill any hanged process and release you memory.

hope it helped.

Regards

ASHFAQ

[sarvjeet]

It could be due to heavy operation by QMC reload tasks. Check if some big QVD is getting loaded in ETL part

To identify the Dashboard memory usage .Try to create Memory usage dumps for dashboard. That will help in identifying the memory issues in dashboard .

[khasimvali85]

Hi Sarvjeet Singh,

Give me Detailed Explanation of Memory Utilisation of Servers

Thanks

Khasim.

[ashfaq_haseeb]

Hi,,

Go through the attache excel sheet for memory calculation.

If you want to see how and where memory utilized more try governance dashboard.

Hope it helped.

Regards

ASHFAQ

[khasimvali85]

Hi,

Give Your Mobile No i Call you at lunch time

Thanks

Khasim.

[ashfaq_haseeb]

ashfaqhaseeb@gmail.com

[Peter_Cammaert]

Add more RAM.

QVS has its own memory manager. QVS will collect and keep every bit of memory that it ever had a need for. The VM size for this process will only grow, except if you restart the service. Only then, memory will be released. Don't worry, this is a good thing.

A QVS size that is often near the absolute max. is indicative of RAM under pressure. Imagine that a big reload job tries to start? it won't get any memory from QVS, and there won't be any spare left in the system.

Ashfaq's spreadsheet can help you in determining the optimal amount of RAM. Note you should add a safe amount for reloads if this platform also runs the QlikView Distribution Service. Add the memory size of the largest reload job (single task chain), or of the largest set of reload jobs that run in parallel.

[khasimvali85]

Hi,

Thanks for giving Suggession, but This Issue has been coming for last 4 days.

[Peter_Cammaert]

In trying to find the root cause: what has changed when these memory spikes first occurred? Did you publish a heavy document? Did you add a lot of new QlikView users?