SESSION_CREATED → OpenDoc takes ~2s (size-independent). Why, and what’s the expected baseline?
We've observed a consistent delay of approximately two seconds when establishing a new WebSocket connection and calling the OpenDoc method, even after the application has been fully loaded into the server's memory and the cache has been calculated. This delay occurs after the qSessionState: "SESSION_CREATED" message but before we receive the initial response containing the app's structure.
Our analysis shows that this delay is not directly proportional to the application's size. For example, we're experiencing a similar two-second latency for a 500 MB application as we are for a much larger 4.5 GB application. While very simple applications may connect within 100-300 ms, there isn't a clear correlation between increased app size and a corresponding increase in this initial connection time. This suggests that the bottleneck is not related to the time it takes to load the app from disk or memory, but rather to another process within the Qlik engine.
We are seeking your expertise to understand the underlying reasons for this consistent delay. Specifically, we'd like to know what internal processes or configurations influence the time it takes for the engine to respond to an OpenDoc request, independent of the application's data size. Understanding this will help us optimize our integrations and improve user experience.
As a related observation, when a second browser tab opens a WebSocket connection to the same app, the connection is established almost instantly. The message qSessionState: "SESSION_ATTACHED" confirms that the new connection is simply attaching to an existing session, which I understand is the expected behavior.
