I don't want to brag, but I've just built #ecl without GC.
-
I don't want to brag, but I've just built #ecl without GC. The build process consumed only 63GB of RAM :3
-
I don't want to brag, but I've just built #ecl without GC. The build process consumed only 63GB of RAM :3
@jackdaniel Did it change anything about the process? (Use of other resources, time required to build the project, etc.) -
@jackdaniel Did it change anything about the process? (Use of other resources, time required to build the project, etc.)
this is work in progress (for modular gc). I had to tweak some configure options, remove a little of bitrot, add six-or-so stubs etc, but nothing severe.
Regarding the process, as I was closing to 64GB (that is exhausting also the swap), I was going through my firefox windows and closing them ^_^.
More seriously though, for programs it was transparent. It has built FFI contribs, ASDF etc without issues. And running produced binary afresh was also working, I've loaded hunchentoot to test whether there are no unexpected regressions.
-
I don't want to brag, but I've just built #ecl without GC. The build process consumed only 63GB of RAM :3
@jackdaniel for a brief moment I read "ed" instead of "ecl" and was like "why the hell would ed require a GC? Oh wait..."
-
I don't want to brag, but I've just built #ecl without GC. The build process consumed only 63GB of RAM :3
@jackdaniel I don't think any other computer related news today will make me smile as much as this.
-
I don't want to brag, but I've just built #ecl without GC. The build process consumed only 63GB of RAM :3
@jackdaniel You should make a bumper sticker "Moore's law is my garbage collector".