The intent when we introduced warmup was to have short activity executed with
low priority after startup to improve user perception of application responsibility.
It should not grow to bigger set of jobs.
It has to be transparent. Code relying on execution of warmup is wrong.
There were several suggestions - tunr it off completely for dev builds, turn off
randomly some parts, rename it from time to time to force contributors to go
Created attachment 39378 [details]