Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We have a single machine where few developers do the development work. sometimes, a developer writes a really bad query that eats up all the resources on the machine and then we can't even login to the machine to kill the process because the memory usage reaches 100% and then there is not even enough memory to login or open the task manager
My question is if it is possible to limit how much memory a single document can use or how much memory in total should the qlikview be using so that we can leave enough memory for the windows server to work normally
Regards
Well, if you let your users develop only in the 32-bit version of Qlikview Desktop then they won't be able to use more than 2GB ram per running instance of Qlikview Desktop. Other than that Qlikview itself does not have any way to set limits. Perhaps you can find a process manager tool for windows somewhere. Maybe this article helps: http://blogs.technet.com/b/clinth/archive/2012/10/11/can-a-process-be-limited-on-how-much-physical-m...
Hi Check out,
Hope this helps,
Thanks,
HirisH
Hi Syed,
i understood your problem.
1) There is no direct way to control RAM utilization(2 gb only/4 Gb only) for Qlikview
2) say to developer ,After writing the script please debug the code with small amount of data here you can easily findout weather our code is having any circular loops or many synthetic tables are there so that u can remove those using by optimization techniques
Note:- RAM usage is more and System is Hang when the script is having Circular loops and synthetic tables.
i hope it will help to u
You could try to limit it with the working set options within the user-properties in tab general (bottom-right). If this don't worked you could try it with the suggestions from Gysbert but it could be a better way not to share a single machine else local machines for each developer and they might use licence lease.
- Marcus
Or move Developers to a real test server with more memory.
And always a great and very cheap technique: tell your developers to keep the Performance tab of Task Manager open at all times or at least during every reload. They won't be running any blind reloads anymore.
Peter