Print

[magneticflux-]

I apologize if this has been answered elsewhere, but I was unable to find a clear answer. I wanted to know if the nbThread int value in AbstractAdaptiveBundler takes into account the peer drivers' nodes' threads when the bundler is representing a peer driver. I checked the source code, and it seems to only use the JPPFProperties.PROCESSING_THREADS property, although a commented-out ternary statement reveals the prior or future presence of a JPPFProperties.PEER_PROCESSING_THREADS property which may be what I'm looking for.
I'm trying to write a version of the ProportionalBundler that better deals with vast differences in channel power, since I have a peer driver with many nodes, and several single-core local nodes.
Thanks,
Mitchell

[lolo]

Hi Mitchell,

This is not done in AbstractAdaptiveBundler, but we do have a specific implementation of this in NodeThreadsBundler. You can see that a different property is used for channels that are peer servers. This property is updated via JMX notifications emitted by the remote peer driver, so it should be up to date most of the time. You can definitely reuse the same mechanism in your own bundler implementation.

I hope this helps,
-Laurent

[magneticflux-]

Thanks! That's exactly what I need! Is there any reason why that property isn't used in AbstractAdaptiveBundler? It seems like it would improve the performance of the algorithm, and the code is there, just commented out.

[lolo]

Indeed, I see no reason why it's not in AbstractAdaptveBundler. Thank you for catching this.
I've registered an enhancement for the upcoming v5.2.2 to this effect: JPPF-478 Improvements in AbstractAdaptiveBundler.

Sincerely,
-Laurent