How many splitting values can auto-baselining handle?
Hi all,
I know in addition to "Application" we can only use one additional dimension, but how many splitting values can the auto-baselining handle? Has this been investigated?
Rick B
Rick are talking about before the auto base-lining would break? Because I would assume it is based off of the Splitting restriction options
My fear is that if I set the splitting restriction too loosely (say max 5000) at some point the mechanism would slow down the server or the PWH operation times
Yeah that seems to make sense to me but I think those numbers may have been chosen as to not slow the entire application down. Whether or not that effects the auto-baselining differently or not I wouldn't know.
Hi Rick,
The limit for the baselining is the same as for a normal BT. By default we cap a business transaction after 5000 split values. But I think your question goes more into the direction of how many splittings all BTs together generate that we have to baseline. Right?
Cheers Klaus
It wasn't but that's a good question! I want to take advantage of this feature more and more, just want to make sure I'm not knocking anything over...
There is no exact threshold available for this as it depends on the sizing of the dt server and also on the number of splittings. What is important to also take into account is that in order to get a baseline each split has to produce enough values. Otherwise you won't get meaning full data. Talking to developers about this we said that in an environment that is running fine up to 50 000 split measures should not hurt but we doubt that this would make sense.
Klaus
