Search
Tuesday, 18th of December 2018, 1:56:26 UTC
2:34:22
stassats
(loop (gc)) exhausting the heap is getting old
2:42:29
stassats
why can't that SB-KERNEL::*GC-EPOCH* be gced
2:54:09
stassats
for some reason each *gc-epoch* resides on its own page
2:55:51
stassats
why is it pinned for more than two calls to (gc)?
3:00:26
stassats
what happens if i write to the old *gc-epoch* cons
3:16:27
stassats
ok, each cons is residing on its own page, using a lot of pages but reporting a low number of bytes used, so it's never reaches the trigger
3:19:11
stassats
i think that's new after we wipe non pinned objects, effectively blowing up usages
3:19:35
stassats
i think the trigger should be changed to the number of pages used, not bytes allocated
3:25:20
stassats
or shouldn't bytes_allocated includes wasted space
3:35:01
pfdietz
This sounds important, and assuming you fix it it should go in monthly release notes.
3:35:29
stassats
eh, i'm not sure it's visible anywhere outside of (loop (gc)), a pathological case
3:35:38
stassats
but i'm using (loop (gc)) for testing
3:38:08
stassats
i suppose i need to prove that first
3:39:22
stassats
by trying to emulate what gc does
3:48:09
stassats
difficult, (loop (gc)) is just too perfect
Tuesday, 18th of December 2018, 13:56:26 UTC