Steven D'Aprano writes:
> ...
> Is anyone able to demonstrate a replicable performance impact due to garbage
> collection?
I have had some experience with the performance impacts of garbage collection
-- not completely replicable but rather frequently visible.
Huge Zope instance (with around 2 G
For some reason, this post from INADA Naoki shows up on the python-list
email archives, but not comp.lang.python, which is what I use.
INADA Naoki wrote at Sat May 14 10:32:12 EDT 2016:
> Mark and Sweep GC is triggered when many new **tracked** objects are
> created and not destroyed.
>
> Since
Steven D'Aprano writes:
> Is anyone able to demonstrate a replicable performance impact due to
> garbage collection?
As Laurent describes, Python uses refcounting, and then does some gc in
case there was dead circular structure that the refcounting missed.
Your example had no circular structure s
Steven D'Aprano wrote:
> Just for kicks, I've been playing around with running code snippets with
> and without the garbage collector enabled, looking to see if it will make
> any obvious difference to performance.
>
> So far, I haven't found any.
>
> For instance, I tried:
>
> a = [i**3 for i
Mark and Sweep GC is triggered when many new **tracked** objects are
created and
not destroyed.
Since integer doesn't have reference to another objects, it's not tracked
object.
So your sample code doesn't show difference of GC.
You can see gc stats via gc.set_debug(gc.DEBUG_STATS).
Play this scr
