Skip to main content
November 19, 2025
Question

Can we make consolidation process faster?

  • November 19, 2025
  • 3 replies
  • 5 views

Hi,

Currently we are not using translation (currency conversion) and I was wondering if we can skip translation process while consolidating or can consolidate only specific accounts (if it allows) to make the process faster?

We have a reporting application with huge set of data and need to refresh the data hourly followed by consolidation which is time consuming process. I am using data management out of the box step for consolidation with C#Aggregated. Can I use any other approach to make it faster?



 

3 replies

November 19, 2025

Hi HoneyGulati​ 

If you are already using C#Aggregated then you are already only aggregating the data e.g skipping consolidation overhead

So for any further gains, it might be worth investigating the Data Unit Size of your application, there is a KB article that explains how to do this.

OneStream Customer Support - How to Investigate and Reduce Data Unit Size

Hope this helps

Sam

November 19, 2025

Hi HoneyGulati​ , if you can, move Entities to create more Siblings in the Entity dimension and reduce the number of Parent Entities if feasible.  OneStream processes sibling Entities concurrently.  If there are any un-necessary Parent members in the Entity dimension, such as a single Parent Entity with only 1 Base Entity, that is a detriment to consolidation speed.  Limiting the number of aggregation points in the Entity dimension would help the overall time.  Also, there are MANY ways to wreck your consolidation times.   i.e Member Formulas, long running calcs.  It begs the question of managing reasonable expectations: "It takes 30 seconds" versus "it takes 10 minutes", and what your expectations are and what is considered too slow to get the reporting hierarchies you need and want at certain aggregation points.

November 21, 2025

Extensibility Series: An Overview of Extensibility in OneStream | OneStream Community
Extensibility Series: Riding the Wave of Vertical Extensibility | OneStream Community
In addition to the points in the past or earlier posts, please find our setups below:
1. Optimization via Levels of Extensibility: 3 Vertical and 2 Horizontal
2. Parallel: the Max # of threads on App Servers - OS Support/SAAS