(imported topic written by cstoneba)
Is it better/more efficient to have 1 big baseline (ie MS Patches) or alot of small baselines (ie MS Patches Aug09, MS Patches Jul09, etc) ?
thanks
(imported comment written by SystemAdmin)
As per the comment in the Deployment Health Checks Dashboard
Baselines with too many components may run slowly on BES Clients and cause slow reporting. The following Baselines have over 100 components and should be reduced in size. Raising the BES Client Setting: Client UI Minimum Analysis Interval can help make the BES Clients handle large Baselines more effeciently.
We have monthly baselines that we deploy for patches, but after a certain amount of time we break them up into baselines for individual patches. While this is time consuming, there is 1 advantage that we found. It give us granular control over the action of a individual hotfix. If a hotfix gets superseded or updated, we do not have to stop the action of a entire baseline to sync the source. If it gets updated, we can stop the action on that one hotfix baseline and test the new source as opposed to stopping a monthly baseline and removing the fixlets for the hotfix that had a binary update.