[perf] explore whether mimalloc would improve performance

[0xdevalias]

⭐ Suggestion

I'm not deeply familiar with things in this area, but stumbled across the following and thought it might be of use:

• perf: use mimalloc for bindings_napi rollup/rollup#5201

  • Description
    This PR swaps the memory allocator with mimalloc.
    This allocator seems to be common in napi-rs world (swc, @napi-rs/fast-escape, parcel, @resvg/resvg-js).
    Some projects uses jemallocator on some OS/architectures and ideally we should check which allocator performs better on each of them. But I'll leave this investigation for now.

    Running the benchmark in Benchmark between rollup v3 and v4 rollup/rollup#5182 (actually I used the esbuild repo instead), I got ~200ms / ~3% improvement on my laptop.

• https://github.com/microsoft/mimalloc

  • mimalloc is a compact general purpose allocator with excellent performance.

[HerringtonDarkholme]

Thanks for the direction! I will try the mimalloc!

[HerringtonDarkholme]

Before

> benches@1.0.0 bench /Users/bytedance/code/ast-grep/benches
> node -r ts-node/register/transpile-only bench.ts

Running "parseSyncBench: Parse One Line" suite...
Progress: 100%

  ast-grep sync parse:
    67 063 ops/s, ±0.86%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Small File" suite...
Progress: 100%

  ast-grep sync parse:
    4 428 ops/s, ±1.45%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Medium File" suite...
Progress: 100%

  ast-grep sync parse:
    221 ops/s, ±9.99%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Huge File" suite...
Progress: 100%

  ast-grep sync parse:
    1 ops/s, ±11.19%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse One Line" suite...
Progress: 100%

  ast-grep async parse:
    25 944 ops/s, ±32.74%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Small File" suite...
Progress: 100%

  ast-grep async parse:
    7 050 ops/s, ±4.79%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Medium File" suite...
Progress: 100%

  ast-grep async parse:
    497 ops/s, ±12.38%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Huge File" suite...
Progress: 100%

  ast-grep async parse:
    3 ops/s, ±8.51%   | fastest

Finished 1 case!

After

Running "parseSyncBench: Parse One Line" suite...
Progress: 100%

  ast-grep sync parse:
    69 787 ops/s, ±0.73%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Small File" suite...
Progress: 100%

  ast-grep sync parse:
    4 355 ops/s, ±4.07%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Medium File" suite...
Progress: 100%

  ast-grep sync parse:
    236 ops/s, ±3.50%   | fastest

Finished 1 case!
Running "parseSyncBench: Parse Huge File" suite...
Progress: 100%

  ast-grep sync parse:
    1 ops/s, ±8.67%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse One Line" suite...
Progress: 100%

  ast-grep async parse:
    20 724 ops/s, ±76.62%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Small File" suite...
Progress: 100%

  ast-grep async parse:
    6 530 ops/s, ±6.70%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Medium File" suite...
Progress: 100%

  ast-grep async parse:
    437 ops/s, ±21.82%   | fastest

Finished 1 case!
Running "parseAsyncBench: Parse Huge File" suite...
Progress: 100%

  ast-grep async parse:
    2 ops/s, ±26.03%   | fastest

Finished 1 case!

I cannot see a reliable difference in napi, though.