Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

The explicit call of gc.collect() #53

Open
andreibogdanflorea opened this issue Jul 20, 2023 · 0 comments
Open

The explicit call of gc.collect() #53

andreibogdanflorea opened this issue Jul 20, 2023 · 0 comments

Comments

@andreibogdanflorea
Copy link

andreibogdanflorea commented Jul 20, 2023

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant