topic Session Inactivity Timeout - Is there a downside to making it more than 30 minutes? in Management & Governance

Session Inactivity Timeout - Is there a downside to making it more than 30 minutes?

davwade1 — Wed, 11 Aug 2021 00:32:11 GMT

Some users have asked me to increase the session timeout to make it longer than 30 minutes. We are using Qlik Sense Enterprise on Windows so I do have that option.

Before I make any changes I was hoping someone would be able to tell me the downside of making the timeout more than 30 minutes. I assume Qlik set this for a specific reason but I have not been able to find any posts or knowledge articles explaining why.

Thanks,

David

Re: Session Inactivity Timeout - Is there a downside to making it more than 30 minutes?

Maria_Halley — Wed, 11 Aug 2021 08:15:28 GMT

If you change the timeout it means that the system might consume more recourses, mostly more RAM.

Apps are not unloaded in memory until all sessions are closed + the application timeout.

So making the timeout longer might keep apps in memory longer.

Also there are also memory consumption to keep the information about the session.

But if you have few Apps that are used by many people the apps are probably in memory anyway so shouldn't make a big difference.

In the end all QlikSense setups are different and you have to test what works best for you.

Re: Session Inactivity Timeout - Is there a downside to making it more than 30 minutes?

davwade1 — Wed, 11 Aug 2021 18:06:48 GMT

Thanks very much for the explanation, that makes perfect sense. I think I will increase the timeout from 30 minutes to 60 minutes. Right now our max RAM hits about 86GB each day and the system has a total of 124GB. I will be sure to monitor the max RAM to ensure it does not get near the total available.

Thanks