Sujet : Re: GIL-Removal Project Takes Another Step (Posting On Python-List Prohibited)
De : greg.ewing (at) *nospam* canterbury.ac.nz (Greg Ewing)
Groupes : comp.lang.pythonDate : 20. Mar 2024, 08:29:30
Autres entêtes
Message-ID : <l5vhisFc622U1@mid.individual.net>
References : 1 2 3 4 5
User-Agent : Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
On 20/03/24 4:14 pm, Lawrence D'Oliveiro wrote:
not to
mention the latency when there isn’t quite enough memory for an allocation
and you have to wait until the next GC run to proceed. Run the GC a
thousand times a second, and the latency is still 1 millisecond.
That's not the way it usually works. If you run out of memory, you
run a GC there and then. You don't have to wait for GCs to occur on
a time schedule.
Also, as a previous poster pointed out, GCs are typically scheduled
by number of allocations, not by time.
-- Greg