Print

[boris.klug]

Hello,

we use local execution for debugging and testing. In our programs we extend the class JPPFResultCollector to collect results while they are finished.

We configured the parameter jppf.local.execution.accumulation.size to specify the number of tasks which are sent at once to the JPPFResultCollector.

The problem is that this does not work. The parameter is ignored. Also the parameter jppf.local.execution.accumulation.time and jppf.local.execution.accumulation.unit are ignored.

We use JPPF 3.3.6 on Windows and Linux, Oracle Java 6 as the JVM.

Thank you for your help in advance.

[lolo]

Hello,

Unfortunately, this functionality disappeared in JPPF 3.2, following a complete redesign of the load-balancing in the client. We never even realized it, shame on us 
I might be able to put it back in the code and release it in the next maintenance release v3.3.8, but it could take quite some time and then I will also have to port it to the 4.0 branch and to the trunk.

Maybe there are ways to achieve what you need without this functionality. Would you mind providing more details on your debugging and testing requirements in this regard?
For instance, the effect provided with "jppf.local.execution.accumulation.size" could be reproduced with specific load-balancer settings in your configuration.
Concretely, instead of:

Code: [Select]

jppf.local.execution.accumulation.size = 8you could set:

Code: [Select]

jppf.load.balancing.algorithm = manual
jppf.load.balancing.profile = manual
jppf.load.balancing.profile.manual.size = 8This will result in the JPPFResultCollector getting no more than 8 tasks at a time.

Sincerely,
-Laurent

[boris.klug]

Noe I had time to do a quick test with JPPF 4.1.2.

For us, setting the load balacining algorithm to manual and than settings the manual.size is good enough.

Thanks for your help (long ago!).