Hi Sheron, memory usage should be about the same as before, except that memory overhead when running tasks is now moved to a separate publisher.
What is the old environments Document Timeout setting? http://help.qlik.com/en-US/qlikview/12.0/Subsystems/QMC/Content/QMC_Documents_UserDocuments_Server_Performance.htm?q=document%20timeout This is the setting that releases applications from memory (8hr default), by reducing this you can lower memory consumption a lot.
Hi Magnus, changing the 480 minutes (8 hrs. from the time the document is published it will be available in memory) will reduce (300 minutes) or increase (720 minutes) memory usage.
Does the "Document timeout" correlates to Sessions? (Example: Maximum Inactive Session Time, Possible Session Timeout, Maximum Total Session Time)
If "Document Timeout" is set for 60 minutes, Possible Session Timeout, Maximum Inactive Secession Time should be set less than 60 minutes?
Hi Arish, Document Timeout is when untouched applications is flushed out of memory. As soon as someone uses the app the count will restart. Maximum Session timeout is time when an non-active session is shut down, after last session of an app times out the Document timeout starts ticking. The maximum session timeout is intertwined with session timeout in the web server. If the web server has a short timeout the user will be disconnected even with a long maximum session timeout in QlikServer.
Read more under documentation on the different timeout settings:
Hope that this helps