Qlik Sense Engine SessionID relation with Using Cache result
Hello everyone i have question related to using calculated cache results according to qlik sense engine sessionID.
AFAIK When user(lets say user X) opens app, initial load of app gets in RAM, then making any selections on the app will be calculated and gets cached into RAM in future use. After that if another user tries to access the same app will not wait for initial load time because its already in RAM and if user X tries to access same app he will not wait the initial load time PLUS will not wait calculation time with the same selections made in previous session. Because its already calculated and stored in RAM.
From now on i need clarification on how SessionID works?
If Same User tries to open same app second time it gets same sessionID. This makes sense because Qlik Sense will recognize user and serve the cache that selections made before and user get advantage of using calculated results.
What happens if somehow sessionID has changed? How Qlik behave in this situation? Lets say we closed the whole browser not browser tab and re-login. This action will force Qlik to get new ProxySessionID from Qlik and accessing same APP will force to get new sessionID. Then user cant reach its pre-calculated result so it has to calculate all the selections again?
Our environment contains huge mashup usage. And when i check logs in C:\ProgramData\Qlik\Sense\Log\Engine\Trace\QLIKSERVER1_Session_Engine.txt i can see that same user accessed the same app but with different SessionID's in short period of time. In this case are we getting advantage of pre-calculated results?
