[issue4687] GC stats not accurate because of debug overhead

Antoine Pitrou added the comment: Thank you. Now committed in r80704 (trunk), r80705 (py3k), r80706 (2.6), r80707 (3.1). -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 3.1, Python 3.2 ___

[issue4687] GC stats not accurate because of debug overhead

Changes by Tres Seaver : -- versions: +Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue4687] GC stats not accurate because of debug overhead

Tres Seaver added the comment: The patch looks obviously correct to me. I can confirm that the patch applies cleanly both to the trunk and to the 'release26-maint' branch, and that the 'test_gc' tests pass in both cases after applying it and rebuilding. -- nosy: +tseaver ___

[issue4687] GC stats not accurate because of debug overhead

New submission from Antoine Pitrou : With gc.DEBUG_STATS, each GC collection displays the elapsed time. Unfortunately, this elapsed time includes the debug overhead itself, most notable the calls to gc_list_size() which can be quite expensive with lots of objects in the older generation. Conseque