TM1 Forum

I don't see in }StatsbyCube - elements Memory Used for Views and Number of Stored Views any information - it shows 0.
I opened views (at first they opened long but the second time much faster), used ViewConstruct (with the same results), I put VMT and VMM in }CubeProperties - in logs I saw
New Stargate created (sometimes I saw after it Destroying stargate - but not in all cases).

So everything shows that Stargate views are created but I can't see it in }StatsbyCube

May be somebody knows why and that can I do to see something more than zero in }StatsbyCube

I presume you turned monitoring on for the server and waited a minute then refreshed.

Of course PerformanceMonitorOn=T

EP_explorer wrote:Of course PerformanceMonitorOn=T

That doesn't actually start performance monitor, it just gives the option of starting it. You still have to right-click on the server in Architect or Perspective and choose Start Performance Monitor.

tomok wrote:That doesn't actually start performance monitor, it just gives the option of starting it. You still have to right-click on the server in Architect or Perspective and choose Start Performance Monitor.

Nope. This parameter does exactly that: automatically starts populating the }Stats control cubes when a server starts.

As to OP's problem... What is your CalculationThresholdForStorage setting? Maybe your cube calculations are simple enough that they are not getting cached? You can try bringing it below the default 50 to see if it changes the stats you are seeing.

The calculation threshold affects when individual calculated or aggregated cells are stored in the calculation cache, which is completely separate from the view cache, which is controlled by the VMM and VMT parameters.

In reality they are related as if you have cached stargates it can make individual calculations (involving e.g. aggregates from other cubes) take fewer steps and thus fall under the threshold. In a similar way if a view is an aggregation of calculated leaf cells and all the leaf cells are already cached it can take less time to create the view, and so fall under the VMT threshold.

The other thing is that changing a single cell in that cube or any upstream cube will clear out both kinds of cache.

Also, if you have TM1.Cube.Stargate.ViewStorage=DEBUG you should see a message similar to "ViewStorage::AddStargate: Stargate (0x1234567812345678) added to ViewStorage (0x1234567812345678)." In the logs when the stargate is cached. If you're not seeing this, you are likely seeing the calculation cache in use and not the view cache.

If I remember correctly, the stargate calc needs to take >5s to get cached anyway. Since nothing is ever simple with TM1 there are probably a number of other gotcha's too.