basically it is possible to use a QVS-Cluster with QV9. It means that you have two and more server with a running QVS on it. In the management console you can cluster them. After that it can be used as it would by one QVS. You dont have to decide on which server the file should be opened.
At the moment we use four server; one which controls the management console and web server for QV and three with QDS and QVS (even if only the QVS is clustered).
I hope you can use this information for you further thoughts.
Hi - we have a 2 server cluster which works very well both web and qvs servers balanced - the web through an ACE switch and the servers through Accesspoint.
I was wondering if you had any "gotcha" notes when upgradign a cluster. I'm assuming we bring down the services on both servers, deinstall both servers, reinstall both servers, but reboot the servers in primary/secondary order. If you have any experience updating cluster servers, I'd be glad to hear it. Thanks!
I would suggest that we put the idea of clustering and running different components of the QlikView platform upon different servers aside for one moment and address the issue of memory usage on one server.
You should not need anymore memory when hosting the document for "normal viewing". If you mean the difference from running a qvw on your desktop QV Developer to hosting it within QVS, you should find the RAM requirements to be similar. You need to allow for about 5% of the total RAM used by the QVW per extra user.
I have an idle QVS and it is using 3.5GB of RAM for the QVS service. Might seem shocking as idle = no users, but QVS is holding a fair QVWs in RAM.
If possible shutdown the QVS service and restart it, and see how much memory you are using. Also inspect the document settings for "preload" option, since you may be preloading a lot of QVWs and this is affecting the total amount of RAM used for your 35mb qvw.
Hi and thanks for your reply, I am currently researching also in the cluster idea.
Now, to your point - after restart, qvs uses twice less RAM, which is quite interesting, however seems normal, having in mind the number of people using it. As for 'preload' option, it is disabled for all documents on the server - if it is settable anywhere in the document settings, please let me know.
Otherwise, the same file on my local PC consumes three timess less RAM, than running under QVS. Of course, the server runs also other documents (needed for reloading), however this does not in any way explain why the memory usage doubles a few hours after qvs is started.
Guess next steps here should be clustering - if anyone has 'best practices' or similar, or any ideas for performance improvement, please feel welcome to comment.
Thanks for your time,