You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you please explain the reasoning behind explicitly calling the collect() method of the garbage collector in ch.py, line 802?
Have you encountered the issue of the memory blowing up during the optimization process?
I am asking this question because I am noticing a big difference in the time taken to optimize a function (especially when the memory is filled with additional objects managed by the collector), and I've tracked the bottleneck to the gc.collect() call.
The text was updated successfully, but these errors were encountered:
Could you please explain the reasoning behind explicitly calling the collect() method of the garbage collector in ch.py, line 802?
Have you encountered the issue of the memory blowing up during the optimization process?
I am asking this question because I am noticing a big difference in the time taken to optimize a function (especially when the memory is filled with additional objects managed by the collector), and I've tracked the bottleneck to the gc.collect() call.
The text was updated successfully, but these errors were encountered: