Optimal Management of Temporary Cubes to improve RAM Efficiency in Procedures

Fethi ZERARA

In my current Board implementations, I rely on temporary cubes extensively due to their impact on readability and performance management. However, I've noticed they can consume considerable RAM, especially during data-intensive procedures.

Given this, I’m wondering: does it make sense to clear the content of temporary cubes immediately after they’re no longer needed within a procedure (when other dataflow steps follow) to help reduce RAM usage? Or is it more efficient to let them persist until the procedure finishes?

I’m looking for insights on best practices regarding temporary cube management, specifically in terms of memory optimization and performance impact.

Helmut Heimann

Hi @Fethi ZERARA ,

in large models and given the circumstances you're describing, I think it definately makes sense to clear those virtual cubes no longer needed if you want to save RAM. There's a reason the clear cube action has been enhanced to be used on virtual cubes ;-)

However, it may take some time before the RAM is actually cleared from the data the virtual cube had—this has to do with Board's (and Windows') Memory Management.

That said: I'd advice to give it a try.

Best,
Helmut