Portal 2 experiences performance issues when executing long-lasting queries across multiple tabs simultaneously, leading to excessive server load. Unlike Flow Client and Studio, which handle concurrent platform usage more effectively, Portal 2 struggles with this multi-tab functionality. This issue needs to be addressed in the upcoming Portal Connect to ensure smoother operations and better resource management.

Proposed solution is to implement a more proactive approach to managing queries in Portal Connect. This should include mechanisms to optimize and balance server load when multiple queries are run in different tabs by the same user. Consider introducing features such as query prioritization, load balancing, and perhaps a more efficient handling of session data. These enhancements will aim to minimize server strain and improve overall responsiveness, ensuring that users can efficiently work across multiple tabs without degrading performance. This improvement is crucial for maintaining a robust and scalable system as user demands and concurrent operations increase.