You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, to optimize for query speed, there is no silver bullet.
The query speed depends on the composition of the view.
Currently, Optimus is optimizing for one view only. It would be better if Optimus would take multiple views into account.
The new Query Time Compared To Orignal Order would be a weighted average over multiple views.
The text was updated successfully, but these errors were encountered:
I would find this useful too as different user groups may look at the cube in different ways, one at a high-level and another at a more granular level like Product and Month on rows and columns.
Would be ideal to be able to execute and test against both views.
Unfortunately, to optimize for query speed, there is no silver bullet.
The query speed depends on the composition of the view.
Currently, Optimus is optimizing for one view only. It would be better if Optimus would take multiple views into account.
The new
Query Time Compared To Orignal Order
would be a weighted average over multiple views.The text was updated successfully, but these errors were encountered: