You can play a little with the working set limits.
The 'optimized' settings depend also on the amount of available RAM on your server and how much RAM is needed by other processes. What you want to avoid is the OS swapping Qlik's application data and cached results to disk.
Re: QlikView Server Min/Max Working Set Considerations
Thanks for the reply, I've indeed seen the Technical brief on QlikView Server Memory Management and CPU Utilization but the whitepaper gave a more detailed breakdown of how the working sets works.
From what I can gather, the justification to 70% and 90% is to "Leave enough room for handling of transients (that is, the amount of RAM temporarily allocated while the engine purges cached result sets) without reaching the max working set".
Am I right to further say that this 20% buffer between 70% and 90% is just to determine how early does the server start purging cached results, because if the unaggregated dataset takes up a substantial amount of memory the global cache memory might start to exceed the working set minimum?
And also I guess one of the assumption is that, when all of the available QVWs is loaded in the server, the unaggregated dataset it takes up in the RAM should not exceed the minimum working set?
Thanks for the clarification so far, its just that I have to justify exactly why am I using this 70-90 configuration