Tradeoffs with Parallel Execution screen property enabled?

Unknown

   While watching the  AD06 - Capsule Optimization and Protection video in the BOARD e-learning section, I discovered the Parallel Execution screen property. I was surprised to learn this screen property is disabled by default. As the name indicates, this feature controls whether layout queries on the same screen are queued or run in parallel. BOARD automatically runs queries for different users in parallel. I now understand multiple queries from the same user run sequentially, by default. After trying other tactics to improve the screen performance, as outlined by Michele Roscelli, I'm curious about the tradeoffs to be aware of if I chose to enable this screen property. On a server with an abundance of resources, I expect this will improve performance. Aside from the resource management, are there other tradeoffs when this screen property is enabled? Are there any tools to effectively monitor resource usage when this feature is enabled?

 

Moritz Funk

I think one tradeoff is, that a single user can occupy all cores on a Server with Long-running Layouts (for example, 8x 5minutes running Layouts).

So for multi-user-Scenarios, the other users must wait for these Long-runners to terminate to get some processor time.

 

I mainly use this function to quickly determine the slowest layout on Screen and focus on optimizing this.

Previous Member

Hello Bob,

 

The parallel execution is not only a matter of performance, but it changes the user's behavior on the screen.

Sometimes you do not want to let the user input data or change selection until all the information on the screen is available. In this case you go with normal execution in series.

Parallel execution is helpful when you use objects like folders that hide part of the layouts that won't be visible anyway until you go and click on the tab..

 

Regards,

 

Antonio

Unknown

Thank you Antonio Speca and Moritz Funk. Those are all important considerations.