Benjamin Feng

`node.js` doesn't support `http_proxy` natively: https://github.com/nodejs/node/issues/8381

Alternatively, run Docker as interactive (`-it`) and it will no longer auto daemonize: `docker run -it --rm -p 127.0.0.1:$PORT:5000 --name guessit guessit/guessit-rest`

Another idea: what if the current metadata remains the same, and the only difference is that each page is a slab? This might be a good hybrid to reap the...

I've been mixing up payload alignment and frame alignment. Consumers only care about payload alignment, but `frame align = payload align - metasize` In order for allocations to be properly...

There are some major disadvantages: 1. Less friendly debugging. Pointers in memory will no longer look like proper pointers. 2. Fewer redundancies. We have some rudimentary error checking to prevent...

This can be in tandem with converting to doubly-linked-list: 1. Frames are at worst 8B aligned on usize=32 machines. Add usize=32 as a compile assertion. 2. Doubly-linked-list has prev/next nodes....

This adds a depressing 1.5K (+60%) to release-fast and 4K (+100%) to release-safe. I can’t see this as being effective even with major hand tuning.

Brain dump of metadata for C-malloc: Each page pointer (ptr % 65536) translates to an index. This should match the page index stored internally by std.WasmPageAllocator. ```zig const Allocation =...

Baselines using `--release-small --strip` but _**not**_ `wasm-strip` or `wasm-opt`: - 610 — `wasm_page_allocator` attached to malloc / free - 520 — `wasm_page_allocator` directly calling reallocFn - 298 — `allocPages` without...

| Current | Compact | Extended | | --- | --- | --- | |  |  |  | | Align by double word only (8B) | **Align...