Page Comparison

...

• Is there any min limit that will consider if the job will create batches or not?
  • Yes there is, up to the environment it might be vary, please ask support for your specific example.
  • For shared production it was tested well that if there is more than 2000 items, then calculation will create batches and then calculate them, if the limit is not met, batches will always return null and calculation will be only performed in the row calculation level.

  • This limit (5000 by default) is set in the

    price fx

    Pricefx configuration file (server/config/pricefx-config.xml) as follows:

    Code Block

           

    <!--  Configuration values applicable if the node is a calculation slave -->

    <calculationSlave>

    <!-- Minimum number of items to process to allow/use distributed mode -->

    <itemThreshold>5000</itemThreshold>

    </calculationSlave>

    
    

•  Is it worth using it in all cases?
  • I would say yes, if you are worried about performance, this is the first point that you should refer to.
• I am unable to use api.addOrUpdate() method in distributed calculation, is there any workaround for this function?
  • Yes there is a api.boundCall() which can be called including batches, but it is not recommended, however if you do it safety then it will make sense (addOrUpdate only specific sort of keys, not the same).
  • Please refer to this link as example of single usage, or this link as example of batching usage.