In a SlicerDicer session using an extended data model, adding a slice by a categorical field with high cardinality causes performance degradation. To optimize for advanced querying on large populations, what strategy should be employed?
A.
Pre-filter the population with criteria to reduce size before slicing
B.
Use measures with aggregation to summarize instead of slicing
C.
Edit the FDM to index the categorical field
D.
Switch to Clarity-based reporting for high cardinality
Slicing by a categorical field with many distinct values can cause performance problems, because the tool must calculate and display a result for every category. Two strategies improve this. Pre-filtering the population with criteria reduces the number of records before the slice is applied, so fewer calculations are required and fewer categories appear. Indexing the categorical field in the data model, which is a change made by the developer, speeds the retrieval and grouping of values. These are the first and third options. Using measures with aggregation to summarize instead of slicing would change the analysis and would not provide the breakdown that the user wants. Switching to Clarity-based reporting would move the requirement into a heavier, less flexible tool and is not an optimization of the session itself. In practice, the user should first consider whether so many categories are needed, since a chart with hundreds of groups is difficult to interpret. Limiting to the most relevant subset or grouping the values into broader categories can make the analysis both faster and clearer.
[Reference: Cogito Fundamentals – SlicerDicer: Optimizing Slices with High Cardinality, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit