Would a small CI cache-regression check be useful here?

[eivindsjursen-lab]

Hi,
I took a look at your Actions/cache setup and it seems like the kind of workflow where cache behaviour can drift without it being very obvious at first, especially when builds still pass but restore/setup time starts moving.

I’ve been testing a small GitHub Action that warns on cache regressions in CI — things like cache key churn, lower reuse, and restore steps getting slower than the baseline — and posts a short summary when behaviour changes between runs.

Not suggesting this as a change to CVAT itself, just thought it might be relevant for your workflow setup.

Repo:
https://github.com/eivindsjursen-lab/gates-suite-public-beta

If useful, I can share a very small warn-only snippet tailored to this kind of workflow?