-
Notifications
You must be signed in to change notification settings - Fork 57
Build Arrow with support for mimalloc and jemalloc #540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| var pool = MemoryPool.GetDefaultMemoryPool(); | ||
|
|
||
| Assert.AreEqual(0, pool.BytesAllocated); | ||
| Assert.Greater(pool.MaxMemory, 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was incorrect even with the system allocator and only passed when other tests had been run previously and allocated memory.
| "name": "parquetsharp", | ||
| "version-string": "undefined", | ||
| "builtin-baseline": "d9ccd77bb554e67137f3f754a2e2f11f4188c82c", | ||
| "builtin-baseline": "e08b7bd89ae162f8579df2f8d39a1ae94107c8fd", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed to bump the baseline to pick up this fix that allows using mimalloc on non-Windows: microsoft/vcpkg#46299
This means the default allocator will now be mimalloc, matching upstream Arrow on platforms where we enable it. Users can switch allocators with the
ARROW_DEFAULT_MEMORY_POOLenvironment variable.Mimalloc and jemalloc should work on arm64, but it appears that these don't build correctly when cross-compiling on an x64 host as part of the Arrow build. Arrow doesn't use mimalloc or jemalloc from vcpkg but always builds its own version, so this probably needs some fixes to the upstream Arrow build scripts.