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
Python is very memory effective because of reference counting (object is freed when refcount drops to zero even with gc.disable) and gc.collect only forces him to run cyclic garbage collector immediately. If it is not acceptable to to remove this call, can we have option to tuning this?
The text was updated successfully, but these errors were encountered:
That line went in in 42fa2b6 where @mdboom notes it makes debugging memory usage easier. However, I am willing to trade 20% on the tests for inflicting pain on the dev who does memory debugging 😈 .
Mostly this is due to this call
Python is very memory effective because of reference counting (object is freed when refcount drops to zero even with
gc.disable
) andgc.collect
only forces him to run cyclic garbage collector immediately. If it is not acceptable to to remove this call, can we have option to tuning this?The text was updated successfully, but these errors were encountered: