This may be common knowledge, but it tripped me up this week.
Over a week ago I was experimenting with six custom models. I had them all loaded in the ‘Custom model folder’ (C:\DeepStack\MyModels). Eventually I settled on using only three of the six models.
Here’s where I made my mistake. I failed to remove the unused models (*.pt files) from the folder. For the past week I started noticing more CPU usage warnings and high RAM usage warnings.
Upon investigating I relearned that DeepStack creates a python.exe instance for each *.pt model in the ‘Custom model folder’ - regardless of whether the models are actually used by a Blue Iris camera.
.
As I had settled on only three custom models, I was allowing DeepStack to use about 5GB of unnecessary RAM to my 16GB system (~1.5GB ‘working set’ RAM per model). In total, my system was using 14/16GB (87% as suggested by the Android app screenshot). After moving the files, I was using 10.7/16GB (66%).
See the attached screenshots for the details.
BEFORE…

AFTER…

Over a week ago I was experimenting with six custom models. I had them all loaded in the ‘Custom model folder’ (C:\DeepStack\MyModels). Eventually I settled on using only three of the six models.
Here’s where I made my mistake. I failed to remove the unused models (*.pt files) from the folder. For the past week I started noticing more CPU usage warnings and high RAM usage warnings.
Upon investigating I relearned that DeepStack creates a python.exe instance for each *.pt model in the ‘Custom model folder’ - regardless of whether the models are actually used by a Blue Iris camera.
.
As I had settled on only three custom models, I was allowing DeepStack to use about 5GB of unnecessary RAM to my 16GB system (~1.5GB ‘working set’ RAM per model). In total, my system was using 14/16GB (87% as suggested by the Android app screenshot). After moving the files, I was using 10.7/16GB (66%).
See the attached screenshots for the details.
BEFORE…



AFTER…



Last edited: