topic What impact does increasing or reducing the Session Timeout have on the server resources? in Management & Governance

What impact does increasing or reducing the Session Timeout have on the server resources?

mwallman — Fri, 18 Oct 2019 08:15:40 GMT

Hello all,

What impact does increasing or reducing the Session Timeout have on the server resources?

For example we have our timeout set to 30mins currently due to low number of apps being consumed.

However I have heard that by lowering the timeout e.g. to 15mins you can save on the CPU/RAM in an environment where there are lots of apps.

Is this a good strategy for such a scenario? Especially where you find users opening lots of apps but not doing much with it.

Re: What impact does increasing or reducing the Session Timeout have on the server resources?

otmane — Fri, 18 Oct 2019 14:15:24 GMT

Hi mwallman,

All i know is that applications are cached when opened for the first time by a user and RAM is released after a certain time when the last user is logged out. but if the user is stiil using Qlik he will login again !

The RAM consumption depends on the App weight and on the number of logged users.

The CPU consumption depends on the app data , app data model and the use of Engine (user selections, actions, ...).

if you have significant feedback or study on the correlation between time out and performance or ressource saving, please share.

Regards

Otmane

Re: What impact does increasing or reducing the Session Timeout have on the server resources?

BTIZAG_OA — Mon, 21 Oct 2019 11:32:47 GMT

Hello,

Im not sure but, you can try to lower QMC>Engine>Apps>App Cache time default value is 8h.

"The number of seconds that a Qlik Sense app is allowed to remain in memory, after the last session that used the app has ended."

as long as people log into qs and opens app into ram it will remain for 8h from last user session ends on app.

https://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/engines-overview.htm

This may saves initial ram reload on server but not usefull for high sized apps..