In debugging Python GC actions, it's really useful to know the amount
of time Python spends doing the GC cycle (i.e. the pause time). I made
a quick hack to do this, and I've attached the patch. It needs to be
fixed to be portable. I wanted to just call floattime() from
timemodule.c, but it wasn't clear how to do this from gcmodule.c.
My patch adds the gc time and the max gc time to the "done" line when
debugging is enabled, making it look like this:
gc: collecting generation 0...
gc: objects in each generation: 702 5608 72421
gc: done. (0.000267006 s, max 0.151359 s)
I'd like to see something like this added to gc module.
I also think it would be useful if there were a debugging mode to
print out gc sweeps which take longer than a certain pause time.
(i.e. gc.debug_pauses (0.2) would print out a line for each gc pause
over 0.2 seconds)
--
David Jeske
Neotonic Software Corporation
email jeske@neotonic. com
phone (415) 701-8003x1
fax (415) 704-3283
of time Python spends doing the GC cycle (i.e. the pause time). I made
a quick hack to do this, and I've attached the patch. It needs to be
fixed to be portable. I wanted to just call floattime() from
timemodule.c, but it wasn't clear how to do this from gcmodule.c.
My patch adds the gc time and the max gc time to the "done" line when
debugging is enabled, making it look like this:
gc: collecting generation 0...
gc: objects in each generation: 702 5608 72421
gc: done. (0.000267006 s, max 0.151359 s)
I'd like to see something like this added to gc module.
I also think it would be useful if there were a debugging mode to
print out gc sweeps which take longer than a certain pause time.
(i.e. gc.debug_pauses (0.2) would print out a line for each gc pause
over 0.2 seconds)
--
David Jeske
Neotonic Software Corporation
email jeske@neotonic. com
phone (415) 701-8003x1
fax (415) 704-3283