Thank you, I’ve seen your new topic and @SergejKipnis is already on it.
I suppose the issue that this thread here is about should also classify as “real bug” - either the 2.0->2.1 cmk-update-config is missing a step and leaves a config that takes ages for the protobuf code to parse, or the new “incremental compile” is broken under certain circumstances.
As mentioned, I didn’t do anything but update 2.0 → 2.1 according to the documentation, and instead of faster activation I get slower activation (I’ve got instances of 78 seconds of activation time sometimes, even if no patch release was installed immediately prior), and anything that is not caused by deliberate action / (mis-)configuration by me is a “real bug” in my understanding.