-
-
Notifications
You must be signed in to change notification settings - Fork 119
Description
Hello! Thank you for your work on this project. I'm currently using the this library inside a Docker container.
Every time I call new Remover(), it takes about 60 seconds to load. Since I'm running this on a system with an RTX 4090 and more than sufficient CPU and RAM, I don't believe the issue is related to hardware limitations.
At first, I thought it might be downloading the model on each call, so I manually downloaded the .pth file and placed it in the expected location—but that didn’t seem to make a huge difference.
Interestingly, after the first new Remover() call in a given container session, subsequent calls only take a few seconds, which is fine.
The issue is that my workflow involves spinning up the container only when I need GPU-related tasks, and shutting it down afterward. This means that I have to call new Remover() from scratch every time, and the 60-second cold start time becomes a bottleneck.
Do you have any idea what might be causing this initial delay? My guess is that new Remover() might be installing some requirements or performing a heavy one-time setup step. If I could identify exactly what’s happening during this call, I could pre-install or cache it in the Docker image to avoid the delay.
Any insight would be greatly appreciated!