[Feature] Report image size differences caused by PR

[eero-t]

Priority

Undecided

OS type

N/A

Hardware type

N/A

Running nodes

N/A

Description

Issue

Small changes or omissions can have large impact on GenAIComps image sizes, but currently such changes can easily go in unnoticed in PR reviews. E.g. forgetting to specify that given Python module indirect dependencies should pull CPU version of PyTorch instead of Nvidia / CUDA one, can increase images size by 3.5 GiB.

Proposed solution

It would help if some automation could provide image size difference information to the PR, for the images that CI determines to be affected by the PR[1].

It would be preferable for size difference to be against latest version in DockerHub, but if that's too hard, a size difference against (e.g. hard-coded info of) image sizes of previous release could be an alternative.

---

[1] Because many things do not specify dependency versions, but just pull in the whatever is latest, rebuilding an image could cause image size change (or functional changes), without any change in OPEA repository content. This is a separate problem though.

[ftian1]

this request does make sense. we can enable it in CICD. @chensuyue pls evaluate it

[chensuyue]

Now we use uv tool freeze the deps version to reduce some of the uncertainty. But it's still worth to monitor image size, I will consider how to enable this in CI.