How to speed up force calculate step?
Hi all,
We are running "force calculate" step to perform force calculation of 80% base entities . It runs for 4-6 hours. How to improve performance , any way run this in multi thread/parallel by e...
Forum Discussion
Thanks Jack, I am already ware of what you said , may I should rephrase my question. I want to know a way to trigger same calc.step in parallel for 5-6 different group of entities that way I can achieve faster execution. Currently we pass value1 and all base entities of value1 is force calc. it has appx 10000 entities underneath. Now value1 is a parent in entity dimension so I am looking for a way to launch from dashboard button in single click, if there is way to run force calc for value1.1, value1.2, value1.3 at same time?
You can run calculations on different servers using data management jobs. There is a selection box for server in data management jobs.
Other tips:
- Member formulas run in parallel.
- You can aggregate instead of consolidate.
- You can run custom calcs in a parallel.ForEach loop from a extender business rule.
- You can avoid aggregating/consolidating multiple periods. Set the base entities (or a subset of it) to dirty with a business rule and then run a standard aggregate/consolidate instead of force. This can be done with a business rule and a data management job.
And of cause you can combine some of these ideas.
Christian, out of curiosity, would triggering custom calculate using a parallel.ForEach run faster compared to triggering a DM Step for 100 entities? I thought the DM Step would also include some sort of parallelization
In general probably not, but in special cases when your knowledge about the calculations allows you to optimise it, it can help.
OneStream tries to calculate entities in parallel and even within a single entity, it tries to calcs all member formulas with the same calc level at the same time, but if your calculations are single entity (I.e top member of a consolidation) and if it is business rule based, it definitely helps, because OneStream can’t parallelise business rules without your help.
