-<p>If your cluster is busy and have significant waiting times you can achieve a faster response by allowing the server machine to calculate small tasks and the reserve the cluster for bigger jobs. This works especially well if your server is a powerful machine with many CPUs. To do this you need to enable and configure both the cluster and the local engines. Once this is done decide on the maximum size of a task to be run on the server locally. Then, edit <span class="hightlight">"# LocalEngineExecutionLimit #" </span>preset in<span class="hightlight"> <ServiceName>Limits.xml</span> file accordingly. JABAWS server then will balance the load according to the following rule: If the task size is smaller then the maximum task size for local engine, and the local engine has idle threads, then calculate task locally otherwise submit the task to the cluster. </p>\r
+<p>\r
+ If your cluster is busy and has significant waiting times, you can achieve a faster response by allowing \r
+ the server machine to calculate small tasks and then reserve the cluster for bigger jobs. This works \r
+ especially well if your server is a powerful machine with many CPUs. To do this you need to enable and \r
+ configure both the cluster and the local engines. Once this is done decide on the maximum size of a task \r
+ to be run on the server locally. Then, edit \r
+ <span class="hightlight">"# LocalEngineExecutionLimit #" </span>preset \r
+ in <span class="hightlight"> <ServiceName>Limits.xml</span> file accordingly. JABAWS server then \r
+ will balance the load according to the following rule: If the task size is smaller than the maximum task \r
+ size for local engine, and the local engine has idle threads, then it calculates task locally otherwise it submit \r
+ the task to the cluster.\r
+</p>\r
+\r