Open hasan7n opened 4 months ago
Thanks for the detailed report!
I am guessing the main_run
buildup could be related to #780, but this needs to be investigated.
FWIW, this is the memory profiler used: https://pypi.org/project/memory-profiler/
FYI, 1 is not in GaNDLF, and is a different library (https://github.com/CBICA/FigureGenerator). Though the underlying dependencies are very similar (SimpleITK and numpy).
Stale issue message
i can tackle this issue
i can tackle this issue
Thanks! I am assuming that this will relate to #780 as well.
When using the FeTS tool (script), we noticed two sources of memory build-up:
main_run
function (lines), around 400MB per call.Further profiling of GaNDLF'S
main_run
showed the information below (note: the profiling was done on GaNDLF's commit616b37bafad8f89d5c816a88f44fa30470601311
)model
variable at the end of the inference loop will resolve this.compiled_model
variable will not resolve this, which suggests that the build-up happens inside the compiled ov library.