Skip to content

The explicit call of gc.collect() #53

@andreibogdanflorea

Description

@andreibogdanflorea

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions