<![CDATA[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?
https://docs.pycom.io/pycom_esp32/library/gc.html

]]>https://forum.pycom.io/topic/1454/at-what-time-should-i-manually-run-gc-collectRSS for NodeSat, 13 Jun 2026 02:39:36 GMTWed, 05 Jul 2017 03:26:53 GMT60<![CDATA[Reply to At what time should I manually run gc.collect()? on Wed, 05 Jul 2017 15:34:06 GMT]]>Should I setup a background thread to just run it every few hundred milliseconds? Is that what the automatic collector does?
Is that reliable?
https://docs.pycom.io/pycom_esp32/library/gc.html

]]>https://forum.pycom.io/post/9124https://forum.pycom.io/post/9124Wed, 05 Jul 2017 15:34:06 GMT<![CDATA[Reply to At what time should I manually run gc.collect()? on Wed, 05 Jul 2017 06:26:07 GMT]]>@BetterAuto
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 gc.collect().

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.

]]>https://forum.pycom.io/post/9127https://forum.pycom.io/post/9127Wed, 05 Jul 2017 06:26:07 GMT<![CDATA[Reply to At what time should I manually run gc.collect()? on Wed, 05 Jul 2017 15:32:38 GMT]]>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?

]]>https://forum.pycom.io/post/9140https://forum.pycom.io/post/9140Wed, 05 Jul 2017 15:32:38 GMT<![CDATA[Reply to At what time should I manually run gc.collect()? on Wed, 05 Jul 2017 18:54:49 GMT]]>@BetterAuto

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.

]]>https://forum.pycom.io/post/9148https://forum.pycom.io/post/9148Wed, 05 Jul 2017 18:54:49 GMT<![CDATA[Reply to At what time should I manually run gc.collect()? on Thu, 06 Jul 2017 19:39:48 GMT]]>@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.

]]>https://forum.pycom.io/post/9162https://forum.pycom.io/post/9162Thu, 06 Jul 2017 19:39:48 GMT<![CDATA[Reply to At what time should I manually run gc.collect()? on Fri, 07 Jul 2017 02:06:51 GMT]]>So it sounds like one risk is latency. What other risks are there from running it?

]]>https://forum.pycom.io/post/9165https://forum.pycom.io/post/9165Fri, 07 Jul 2017 02:06:51 GMT