One of the benefits of using IIS is to allow your ApplicationPool to spawn more workers if the load is high. Can this be applied for QlikView as well? No, ?adding more workers in IIS is not recommended.
When allowing more than one (1) worker process, session states need to be stored outside the process.
Example:
-
InProc mode, which stores session state in memory on the Web server. This is the default. This is the one used by Qlik
-
StateServer mode, which stores session state in a separate process called the ASP.NET state service. This ensures that the session state is preserved if the Web application is restarted and also makes the session state available to multiple Web servers in a Web farm.
-
Off mode, which disables session state.
See Microsoft for details.
Applying anything other than InProc leads to QlikView (QvAjaxZfc / Full Browser Client) reconnecting.
Environment:
The QlikView AccessPoint is not built using asp.net, so we do not use the asp.net session object. Therefore it doesn’t help to set the IIS to store session state outside of memory, Our session information is stored in memory so if multiple worker processes are configured, they have different memory space. If the worker process assigned to the user is then directed to different memory space, QlikView will need to reconnect.
Adding more workers in IIS is not recommended.
