[issue4687] GC stats not accurate because of debug overhead

2010-05-02 Thread Tres Seaver
Tres Seaver tsea...@agendaless.com 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. --

[issue4687] GC stats not accurate because of debug overhead

2010-05-02 Thread Tres Seaver
Changes by Tres Seaver tsea...@agendaless.com: -- versions: +Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4687 ___ ___

[issue4687] GC stats not accurate because of debug overhead

2010-05-02 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr 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

2008-12-17 Thread Antoine Pitrou
New submission from Antoine Pitrou pit...@free.fr: 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