> Note that pybench disables GC per default for exactly the reasons
> causing #4074 :-)

I know, I was thinking to enable the GC only in the GC-specific test of
course. The idea is to have a test stressing the GC heavily, such as the
example code in #4074.

The reason I suggest doing it in pybench is that it offers existing
facilities for measuring execution times, agregating results etc.

> Regarding memory management: The exact amount of used memory is hard to
> determine from within a process due to the way e.g. Linux or other
> modern OSes manage memory.

I was not thinking about measuring the amount of used memory but rather
the time spent in specific tests which would focus on the CPU cost of
memory allocation rather than computation or control flow. Something
like allocating lots of strings or tuples of various sizes, then
releasing them in various orders.