1 result found

1. Enhanced Concurrent Sessions in Portal Connect

   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.

   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,… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   declined  ·  AdminMalin Johansson (Admin, Novacura) responded

   The backend for Flow Connect is significantly different from Flow Classic, with performance being one of our main areas of improvement. We have introduced features like running the client in the browser and added caching layers. Further enhancements will be made in the future based on user requirements and feedback from Flow Connect users.

   
   

   We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.