Because a single ContinuouslyChanging node forces the entire node group to evaluate every frame, it can cause innocent-looking code to cause major performance loss in certain contexts.