Gregory Ewing :
> Lawrence D’Oliveiro wrote:
>> what WOULD you consider to be so “representative”?
>
> I don't claim any of them to be representative. Different GC
> strategies have different characteristics.
My experiences with Hotspot were a bit disheartening. GC is a winning
concept provided t
Lawrence D’Oliveiro wrote:
what WOULD you consider to be so “representative”?
I don't claim any of them to be representative. Different GC
strategies have different characteristics.
--
Greg
--
https://mail.python.org/mailman/listinfo/python-list
On Jun 22, 2017 4:03 PM, "Chris Angelico" wrote:
On Fri, Jun 23, 2017 at 5:22 AM, CFK wrote:
> On Jun 22, 2017 9:32 AM, "Chris Angelico" wrote:
>
> On Thu, Jun 22, 2017 at 11:24 PM, CFK wrote:
>> When
>> I draw memory usage graphs, I see sawtooth waves to the memory usage
which
>> suggest that
On Fri, Jun 23, 2017 at 5:22 AM, CFK wrote:
> On Jun 22, 2017 9:32 AM, "Chris Angelico" wrote:
>
> On Thu, Jun 22, 2017 at 11:24 PM, CFK wrote:
>> When
>> I draw memory usage graphs, I see sawtooth waves to the memory usage which
>> suggest that the garbage builds up until the GC kicks in and re
On Jun 22, 2017 9:32 AM, "Chris Angelico" wrote:
On Thu, Jun 22, 2017 at 11:24 PM, CFK wrote:
> When
> I draw memory usage graphs, I see sawtooth waves to the memory usage which
> suggest that the garbage builds up until the GC kicks in and reaps the
> garbage.
Interesting. How do you actually
On Thu, Jun 22, 2017 at 11:24 PM, CFK wrote:
> When
> I draw memory usage graphs, I see sawtooth waves to the memory usage which
> suggest that the garbage builds up until the GC kicks in and reaps the
> garbage.
Interesting. How do you actually measure this memory usage? Often,
when a GC frees u
On Jun 22, 2017 12:38 AM, "Paul Rubin" wrote:
Lawrence D’Oliveiro writes:
> while “memory footprint” depends on how much memory is actually being
> retained in accessible objects.
If the object won't be re-accessed but is still retained by gc, then
refcounting won't free it either.
> Once agai
Lawrence D’Oliveiro writes:
> while “memory footprint” depends on how much memory is actually being
> retained in accessible objects.
If the object won't be re-accessed but is still retained by gc, then
refcounting won't free it either.
> Once again: The trouble with GC is, it doesn’t know when
On Thu, 22 Jun 2017 10:30 am, Lawrence D’Oliveiro wrote:
> Once again: The trouble with GC is, it doesn’t know when to kick in: it just
> keeps on allocating memory until it runs out.
Once again: no it doesn't.
Are you aware that CPython has a GC? (Or rather, a *second* GC, apart from the
refer
