-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update mimalloc, enable for glibc Linux aarch64, explicitly disable for wasm and musl #8462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
🟢 Turbopack Benchmark CI successful 🟢Thanks |
✅ This change can build |
bgw
force-pushed
the
bgw/mimalloc-updates
branch
from
June 12, 2024 23:29
b0d84b5
to
bfcbb2b
Compare
bgw
added a commit
to vercel/next.js
that referenced
this pull request
Jun 12, 2024
This was previously disabled on aarch64-unknown-linux-musl and wasm, due to compilation errors. I moved the logic to disable mimalloc on these platforms into the turbo-tasks-malloc crates in vercel/turborepo#8462 In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator.
ForsakenHarmony
approved these changes
Jun 13, 2024
kdy1
approved these changes
Jun 13, 2024
|
…or wasm and musl - mimalloc seems to work just fine with Linux on aarch64 with glibc - This is already disabled for wasm and musl in next-swc, but I want to centralize these platform checks: https://github.com/vercel/next.js/blob/73918c6711b538678dd66303fdbd61bfd10b288c/packages/next-swc/crates/napi/src/lib.rs#L71
The two implementations were identical, aside from the allocator used. Move the compile-time branch into an inlined function.
bgw
force-pushed
the
bgw/mimalloc-updates
branch
from
June 14, 2024 03:09
bfcbb2b
to
cf91231
Compare
bgw
added a commit
to vercel/next.js
that referenced
this pull request
Jun 14, 2024
This was previously disabled on aarch64-unknown-linux-musl and wasm, due to compilation errors. I moved the logic to disable mimalloc on these platforms into the turbo-tasks-malloc crates in vercel/turborepo#8462 In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator.
bgw
added a commit
to vercel/next.js
that referenced
this pull request
Jun 14, 2024
This was previously disabled on `aarch64-unknown-linux-musl` and `wasm`, due to compilation errors. I moved the logic to disable `mimalloc` on these platforms into the `turbo-tasks-malloc` crates in vercel/turborepo#8462 (which this PR depends on). In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator. **Depends on:** vercel/turborepo#8462 Included turbopack changes: * vercel/turborepo#8409 <!-- hrmny - fix(turbopack-ecmascript-runtime): prevent hanging when top level await is skipped --> * vercel/turborepo#8466 <!-- hrmny - fix(turbopack): make external module wrapper return not found instead of panicking --> * vercel/turborepo#8469 <!-- hrmny - fix(turbopack): add ecmascript options to mdx --> * vercel/turborepo#8447 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.93.4` --> * vercel/turborepo#8472 <!-- Donny/강동윤 - feat: Reduce the number of parts created by tree shaking --> * vercel/turborepo#8480 <!-- Will Binns-Smith - Publish `@vercel/devlow-bench` --> * vercel/turborepo#8481 <!-- Will Binns-Smith - chore: release npm packages --> * vercel/turborepo#8462 <!-- Benjamin Woodruff - Update mimalloc, enable for glibc Linux aarch64, explicitly disable for wasm and musl -->
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
…or wasm and musl (vercel/turborepo#8462) # Description - **Update mimalloc** dependency. - **Enable mimalloc for Linux on aarch64 with glibc:** it seems to work just fine! - **Disable mimalloc for wasm and musl.** Mimalloc is already disabled for these platforms in next-swc, but I want to centralize these platform checks: https://github.com/vercel/next.js/blob/73918c6711b538678dd66303fdbd61bfd10b288c/packages/next-swc/crates/napi/src/lib.rs#L71 - **Reduce duplicate code across platforms.** The two implementations of `TurboMalloc` were identical, aside from the base allocator used. Move the compile-time branch into an inlined function. **Related Next.JS PR:** #66815 # Testing ## On glibc Linux aarch64 ``` pnpm pack-next ``` Install into a test project and try running the development server. ## Other platforms I have not tested other platforms, and will rely on CI for those (here and in #66815)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…or wasm and musl (vercel/turborepo#8462) # Description - **Update mimalloc** dependency. - **Enable mimalloc for Linux on aarch64 with glibc:** it seems to work just fine! - **Disable mimalloc for wasm and musl.** Mimalloc is already disabled for these platforms in next-swc, but I want to centralize these platform checks: https://github.com/vercel/next.js/blob/73918c6711b538678dd66303fdbd61bfd10b288c/packages/next-swc/crates/napi/src/lib.rs#L71 - **Reduce duplicate code across platforms.** The two implementations of `TurboMalloc` were identical, aside from the base allocator used. Move the compile-time branch into an inlined function. **Related Next.JS PR:** #66815 # Testing ## On glibc Linux aarch64 ``` pnpm pack-next ``` Install into a test project and try running the development server. ## Other platforms I have not tested other platforms, and will rely on CI for those (here and in #66815)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
…or wasm and musl (vercel/turborepo#8462) # Description - **Update mimalloc** dependency. - **Enable mimalloc for Linux on aarch64 with glibc:** it seems to work just fine! - **Disable mimalloc for wasm and musl.** Mimalloc is already disabled for these platforms in next-swc, but I want to centralize these platform checks: https://github.com/vercel/next.js/blob/73918c6711b538678dd66303fdbd61bfd10b288c/packages/next-swc/crates/napi/src/lib.rs#L71 - **Reduce duplicate code across platforms.** The two implementations of `TurboMalloc` were identical, aside from the base allocator used. Move the compile-time branch into an inlined function. **Related Next.JS PR:** #66815 # Testing ## On glibc Linux aarch64 ``` pnpm pack-next ``` Install into a test project and try running the development server. ## Other platforms I have not tested other platforms, and will rely on CI for those (here and in #66815)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
…or wasm and musl (vercel/turborepo#8462) # Description - **Update mimalloc** dependency. - **Enable mimalloc for Linux on aarch64 with glibc:** it seems to work just fine! - **Disable mimalloc for wasm and musl.** Mimalloc is already disabled for these platforms in next-swc, but I want to centralize these platform checks: https://github.com/vercel/next.js/blob/73918c6711b538678dd66303fdbd61bfd10b288c/packages/next-swc/crates/napi/src/lib.rs#L71 - **Reduce duplicate code across platforms.** The two implementations of `TurboMalloc` were identical, aside from the base allocator used. Move the compile-time branch into an inlined function. **Related Next.JS PR:** #66815 # Testing ## On glibc Linux aarch64 ``` pnpm pack-next ``` Install into a test project and try running the development server. ## Other platforms I have not tested other platforms, and will rely on CI for those (here and in #66815)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 14, 2024
This was previously disabled on `aarch64-unknown-linux-musl` and `wasm`, due to compilation errors. I moved the logic to disable `mimalloc` on these platforms into the `turbo-tasks-malloc` crates in vercel/turborepo#8462 (which this PR depends on). In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator. **Depends on:** vercel/turborepo#8462 Included turbopack changes: * vercel/turborepo#8409 <!-- hrmny - fix(turbopack-ecmascript-runtime): prevent hanging when top level await is skipped --> * vercel/turborepo#8466 <!-- hrmny - fix(turbopack): make external module wrapper return not found instead of panicking --> * vercel/turborepo#8469 <!-- hrmny - fix(turbopack): add ecmascript options to mdx --> * vercel/turborepo#8447 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.93.4` --> * vercel/turborepo#8472 <!-- Donny/강동윤 - feat: Reduce the number of parts created by tree shaking --> * vercel/turborepo#8480 <!-- Will Binns-Smith - Publish `@vercel/devlow-bench` --> * vercel/turborepo#8481 <!-- Will Binns-Smith - chore: release npm packages --> * vercel/turborepo#8462 <!-- Benjamin Woodruff - Update mimalloc, enable for glibc Linux aarch64, explicitly disable for wasm and musl -->
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 15, 2024
This was previously disabled on `aarch64-unknown-linux-musl` and `wasm`, due to compilation errors. I moved the logic to disable `mimalloc` on these platforms into the `turbo-tasks-malloc` crates in vercel/turborepo#8462 (which this PR depends on). In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator. **Depends on:** vercel/turborepo#8462 Included turbopack changes: * vercel/turborepo#8409 <!-- hrmny - fix(turbopack-ecmascript-runtime): prevent hanging when top level await is skipped --> * vercel/turborepo#8466 <!-- hrmny - fix(turbopack): make external module wrapper return not found instead of panicking --> * vercel/turborepo#8469 <!-- hrmny - fix(turbopack): add ecmascript options to mdx --> * vercel/turborepo#8447 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.93.4` --> * vercel/turborepo#8472 <!-- Donny/강동윤 - feat: Reduce the number of parts created by tree shaking --> * vercel/turborepo#8480 <!-- Will Binns-Smith - Publish `@vercel/devlow-bench` --> * vercel/turborepo#8481 <!-- Will Binns-Smith - chore: release npm packages --> * vercel/turborepo#8462 <!-- Benjamin Woodruff - Update mimalloc, enable for glibc Linux aarch64, explicitly disable for wasm and musl -->
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 16, 2024
This was previously disabled on `aarch64-unknown-linux-musl` and `wasm`, due to compilation errors. I moved the logic to disable `mimalloc` on these platforms into the `turbo-tasks-malloc` crates in vercel/turborepo#8462 (which this PR depends on). In addition to centralizing mimalloc platform support logic, this means that we can get allocation data from these platforms while using the system allocator. **Depends on:** vercel/turborepo#8462 Included turbopack changes: * vercel/turborepo#8409 <!-- hrmny - fix(turbopack-ecmascript-runtime): prevent hanging when top level await is skipped --> * vercel/turborepo#8466 <!-- hrmny - fix(turbopack): make external module wrapper return not found instead of panicking --> * vercel/turborepo#8469 <!-- hrmny - fix(turbopack): add ecmascript options to mdx --> * vercel/turborepo#8447 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.93.4` --> * vercel/turborepo#8472 <!-- Donny/강동윤 - feat: Reduce the number of parts created by tree shaking --> * vercel/turborepo#8480 <!-- Will Binns-Smith - Publish `@vercel/devlow-bench` --> * vercel/turborepo#8481 <!-- Will Binns-Smith - chore: release npm packages --> * vercel/turborepo#8462 <!-- Benjamin Woodruff - Update mimalloc, enable for glibc Linux aarch64, explicitly disable for wasm and musl -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
TurboMalloc
were identical, aside from the base allocator used. Move the compile-time branch into an inlined function.Related Next.JS PRs: vercel/next.js#66815 (reverted) and vercel/next.js#66885 (second attempt with fixes to the next.js CI)
Testing
On glibc Linux aarch64
Install into a test project and try running the development server.
Other platforms
I have not tested other platforms, and will rely on CI for those (here and in vercel/next.js#66815)