Slow cubeviews for prior year balances
We use the REST api to retrieve balances from our accounting consolidations in onestream.
I've noticed that for the current year, these account balances can be retrieved quickly. But for prior ...
Forum Discussion
I'm forwarding the question to the accountants who manage this environment. I'm a software developer and what you describe isn't totally clear.
Recap:
Whatever the problem with balances, it causes data to be slower to retrieve in prior years. It is not a linear deterioration in performance. It is almost exponential. IE. 2023 is 1.5x slower than 2024. And 2022 is 1.5 x slower than 2023.
Most storage formats that I've ever worked with would NOT cause us to pay such a substantial penalty in performance for a prior year. Especially given that OS is a CPM tool, it should be more natural to retrieve a historical trend of our balance sheet accounts, without worrying about the differences in performance by year.
In my experience, the only thing that might incur an exponential performance impact is some sort of dynamic calculation that has MORE work to do for prior years than it does in the current year. Is that true of the "workflows"? What dynamic work is it doing, while retrieving balances? Is there any option to get the balances *without* doing any unnecessary/additional work?
Henning
OneStream Employee
OneStream EmployeeThe reason why I am asking about Closed Workflows is that this moves information to _history tables which are not queried in memory like non-closed workflow related data. So if all workflows have been closed, that would be the easiest explanation for what you observed.
Other than that, it can be many things and one would need to be looking at how the data is queried in the first place and then dissect the different pieces.