topic Re: Does adding an = to a Dimension field make it less efficient? in App Development

Does adding an = to a Dimension field make it less efficient?

mwallman — Fri, 06 Jul 2018 12:33:16 GMT

Hello all,

I seem to recall reading somewhere that adding an = before a Dimension field is not a good practise, is this true?

E.g. Let's say it's a chart of Sales by Country.

Instead of simply adding the Country field as a Dimension, if you make it =Country as Dimension, is this bad?

Re: Does adding an = to a Dimension field make it less efficient?

sunny_talwar — Fri, 06 Jul 2018 12:45:59 GMT

I don't think so... but hic‌ might be a better equipped to answer this

Re: Does adding an = to a Dimension field make it less efficient?

mwallman — Mon, 09 Jul 2018 12:49:17 GMT

It would be great to know.

So many applications I have seen have this.

I was under the impression it calculates the dimension when it is with an = so it is not good for performance.

Re: Does adding an = to a Dimension field make it less efficient?

hic — Wed, 11 Jul 2018 11:05:19 GMT

I doubt that it makes any noticeable difference.

An equals sign does imply that a calculation is made, which could add some overhead. On the other hand - we have several optimization measures in place, so I think that also with an equals sign, the dimension will execute according to the same algorithm.

But I haven't tested it.

HIC