I guess Victa is their own QlikView partner.
So as an alternate route, QlikTech has a few nice documents that handle scalability in detail. The best of which is this one: QlikView Scalability Overview technology whitepaper
We have used this information to size a few machines and to good results.
In addition to the above I would suggest that you investigate what is happening with your setup currently, it may well help your sizing before you splash any cash. A few questions that you could ask yourself are:
- What makes you say you memory floods every time ?
- You do not mention any End User performance issues. Do they have them ? If so any trends to them, as in maybe time of day............. ?
- What is running on the server ? You mention QV Server & NPrinting, are they both on the same server ? Anything like QV Publisher or anything else ?
- Publisher aside, how, on what server & on what schedule do you refresh your QVD's? Weekly? Daily? Hourly? Every minute ?
- When was the server last rebooted ? QlikView does run on MS Windows which every now then needs rebooting as opposed to Linux where 1,000+ days uptime is common. [Don't get me wrong I do think QlikView on Windows is a great product, although if I hear the infamous QV.Next supports Linux I will be most pleased]
- Where do you develop your qvw's & NPrinting ? [I sure hope it ain't on your Production Server]
- Have you analysed your qvw's? Rob Wunderlich's document analyser Downloads - Rob Wunderlich Qlikview Consulting is a great tool.
Notwithstanding the above your current server spec is certainly small. QlikView is a Multithreading, In Memory Tool and certainly needs a fair whack of CPU grunt & RAM. I was talking to somebody earlier this week who is planning upgrading their Server from 500GB to 1 TB of RAM, although she was talking about a lot more users than you.
Best Regards, Bill