Welcome back, for those who had read Part A of this blog, hope you would have tested Parallel Interaction and benefitted from it. For those who haven’t, you can read it at http://blog.octanesolutions.com.au/caveat-around-concurrent-data-loads-part-a
This blog builds upon the previous one and focusses on improving performance by Parallel Interaction, it highlights TM1 facets worth consideration while an object is locking.
Synopsys
Tips towards improvements around support for concurrent read/write and/or parallel execution of turbo integrator process enabling higher efficiencies and productivity.
Analysis
This allows to run a Turbo Integrator process without locking when executed by concurrent users simultaneously.
This nullifies the chance of a query or process triggering a cube dependency; this usually happens during periods of user activity that may block objects and cause contention issues for concurrent reads and writes.
To establish a cube dependency, include AddCubeDependency function and valid only in the Turbo Integrator process. This function creates a manual dependency between two cubes in the model.
Syntax: AddCubeDependency('CubeA','CubeB');
|
Argument |
Description |
|
CubeA |
The name of the base cube. |
|
CubeB |
The name of the dependent cube. |
Cube B relies on a rule that is dependent on Cube A.
This will increase the speed of Turbo Integrator process as it stores a stargate view in memory on the server. The purpose of ViewConstruct function is to cache the view by pre-calculating and storing large views for quick retrieval post a data load or update.
Syntax: ViewConstruct(CubeName, ViewName);
|
Argument |
Description |
|
CubeName |
The cube from which you want to construct the view. |
|
ViewName |
The view you want to construct. This view must be an existing public view on the server. |
This places locks on read and write operations in any cube that includes dimension updates. Thrashing may result in locks during dimension maintenance (read/write to dimensions) as part of executing the Turbo Integrator process.
Note: Do not include dimension maintenance as part of data upload or updates.
This again places locks on read and write in any cube that includes dimension updates.
Thrashing may result in locks during dimension maintenance (read/write to dimensions) as part of executing the Turbo Integrator process.
Note: Do not include attribute alias maintenance as part of data upload or updates.
For more Information: To check on your existing Planning Analytics (TM1) entitlements and understand “how to”, reach out to us at info@octanesolutions.com.au.
Octane Software Solutions Pty Ltd is an IBM Registered Business Partner specializing in Corporate Performance Management and Business Intelligence. We provide our clients advice on best practices and help scale up applications to optimise their return on investment. Our key services include Consulting, Delivery, Support and Training.
Octane has its head office in Sydney, Australia as well as offices in Canberra, Bangalore, Gurgaon, Mumbai, and Hyderabad.
Get a free one-hour consultation on us
To know more about us visit, OctaneSoftwareSolutions.