Skip to main content
chandu_shekar
Newcomer
Jan 10, 2025 10:05 AM UTC

performance issue.

Hello OneStream Community,

I am working with a Cube View where I need to display the Income Statement data for the end of every year (December). The data should show up as the beginning balance for the January month in the subsequent year. To achieve this, I used a Row Override1 member filter with the formula T#povprioryearm12.

The Cube View includes four dimensions: Entity, Division, Cost Center, and Accounts. However, I am experiencing slow loading times when the view is being accessed. it is not exporting to Excel to validate.

I would like to know if there are any best practices or strategies for improving the performance of the Cube View in this scenario. Are there specific optimizations I should consider for the member filter, the dimensions, or the Cube View configuration to reduce loading times?

Any advice or recommendations would be greatly appreciated!

Thank you in advance!

3 replies

Employee - Guide
chulEmployee - Guide
Employee - Guide
Jan 13, 2025 5:03 PM UTC

Hello, I'm unsure of your objective with the cube view. The two main suggestions I can provide are to exclude data unit dimensions in the rows and nest fewer dimensions in the rows.

chandu_shekarAuthor
Newcomer
Jan 16, 2025 1:05 PM UTC

the requirement is all the four dimensions(Entity, Division, CostCenter, Accounts) need to be exist in the cube view.

OneStream Employee
FredLucasOneStream Employee
OneStream Employee
Jan 16, 2025 2:06 PM UTC

Hi chandu_shekar,

Generally, one very important setting with regards to Cube View performance is the "Allow Sparse Row Suppression" that should be set to True both on the General Settings and the appropriate Columns (together with the "Use To Determine Row Suppression" setting).

However, reading your post (and without knowing your data model, data volumns, etc.) it sounds like this might be classed more like a data dump than an actual report. If your goal is to export this data to a .csv file for reconciliation or other purposes you might want to consider using a DM job with a Export Data Step instead.

Terms & ConditionsAccessibility statement