The performance and CO2 profiling is an extensive and welcomed addition to Baler. However the packages needed to run it, together with pyTorch, create very big docker and poetry images. And some are not supported on M1 MAC chip sets maching it impossible for some to run Baler locally.
I propose that we move profiling from the baler core repository to its own repository, still within the baler-collaboration.
The performance and CO2 profiling is an extensive and welcomed addition to Baler. However the packages needed to run it, together with pyTorch, create very big docker and poetry images. And some are not supported on M1 MAC chip sets maching it impossible for some to run Baler locally.
I propose that we move profiling from the baler core repository to its own repository, still within the baler-collaboration.