eCo

it seem this device may be very useful for many situations, however i have a suspicion that it may cause trouble in other situations. let me explain:
from what i have noticed, sometimes the activation of devices/plugins causes cpu spikes.
sometimes i have a Live Set which is using high (but not extreme) amounts of the cpu, without suffering from audio dropouts while everything is playing.
however, if i have paused the set at a busy part of the arangement, the moment i press Play, it will have a momentary glitch before settling down and stabilizing for the rest of the session.
similarly, if a Set is playing with just a few of the tracks active, for example in the intro, if a lot of other tracks kick in simultaneously (or maybe just a couple of heavy ones), the same will happen, ie: momentary glitch before settling down to the proper cpu consumption.
if this is the case, then using "eCo/eCo-m" would possibly intensify this problem?
i may be wrong about this, and i certainly don't want to discourage anyone from using this device.
i would love to use it myself, if i did not have this concern.
i may have a misunderstanding of why this is happening, for example it may not be directly related to devices/vst's sudden activation, but something to do with intel TurboBoost having to activate, or it may be something specific to my pc (which has a 1st gen i5), so i would prefer if someone tested for themselves than take my word for it.
i will also put it in my bookmarks and test it when i have time

ps:
while writing these lines, it occurred to me that it may be the fault of Clips activating, but then again, it also happens when just in arrangement mode.