At what time should I manually run gc.collect()?
Should I setup a background thread to just run it every few hundred milliseconds? Is that what the automatic collector does?
Is that reliable?
So it sounds like one risk is latency. What other risks are there from running it?
papasmurph last edited by
@BetterAuto In one project I shut off automatic garbage collection and then called collect after each loop of measuring time with an ultrasound distance detector, to secure (as well as possible) that the timing wouldn't go wonky.
livius last edited by
Any reason not to just have it running in the background every few hundred milliseconds?
then it can run in your time critical point and brake your logic...
better have control when and where in the code it run.
Any reason not to just have it running in the background every few hundred milliseconds? It can check mem_free and auto-run. I can fork off a new thread and have it constantly run. Is that what the automatic collector does?
livius last edited by livius
There is not good answer to this question.
As always it depends.
But if you have infinite "main" loop
then it is good practice if you put
gc.collect()at least once.
I say depends, because if you have some intensive memory operation
you probably need to run it more the times.
You can also monitor
gc.mem_free()and after mem go to some level run
You also can go in oposite direction and do not run it at all. It "should" be run automatically but then it can run in your time critical point and brake your logic.