Lately I’ve been digging into an old Qlik performance question. How much impact, if any, does the order of Qlik data tables have on chart calc time? My experience is that for a chart or aggr() cube with a lot of dimension values, ordering of rows by dimension values can have a significant and measurable effect.
Mike Steedle of Axis Group blogged about the issue a couple of years ago. Mike’s post includes a useful subroutine to organize any table by a specific field.
I’ve added my own study and sample files on the topic in this QlikCommunity post.
Mike and I are are working together on the next update to Qlik Sense Document Analyzer. Mike is keen on analyzing the data model and making useful recommendations. One of the optimization questions we are studying is whether it is possible to make a solid recommendation on data table organization.
I’m curious to hear what others have discovered on the topic. Do you have any rules you follow in ordering table rows? Any thresholds or object/expression scenarios where you find it’s worth the trouble to manage the ordering?