long-running views (> 1000 secs) seems to roll back

[djkelleher123]

For certain large views, the process seems to roll back:

2021-03-05 12:56:51,872 - optimuspy - INFO - Skipping cube 'group_le_planning' since view '____long_opening_view' does not exist
2021-03-05 12:56:52,047 - optimuspy - INFO - Starting analysis for cube 'group_planning'
2021-03-05 12:56:52,074 - optimuspy - INFO - Original dimension order for cube 'group_planning' is: '['scaling', 'group_view', 'group_layer', 'group_account', 'group_function', 'group_performance_segment', 'group_region', 'gs_gaap_code', 'group_scenario', 'projection_type', 'submission_version', 'currency', 'period', 'value']'

stuck here

I believe that the code that is retriggered is

self.tm1.cells.create_cellset_from_view(cube_name=self.cube_name, view_name=view_name, private=False)

Is there a time limit to this function?

[MariusWirtz]

Hi,

by default, there is no time limit. The view gets executed multiple times per permutation. Ideally, you choose a view that takes ~10-20 sec to load. Large enough to produce meaningful results and measurable differences but not too large to slow it down.

PS
to speed things up, make sure you use the fast mode. Determining the first and the last position has the most impact.