Skip to content

Conversation

@redforks
Copy link
Contributor

@redforks redforks commented Nov 6, 2025

I found that at least in linux, use jemalloc saves a lot of memory, although zed uses much lesser memory than vscode or other ides, but saves memory is a good thing, especially when use with rust-analyzer, less swap usage and better responsibility and faster cargo builds.

And Maybe not use system allocator to build bundles, it is much better in speed and memory usage no matter use mimalloc or jemalloc

Release Notes:

  • N/A or Added/Fixed/Improved ...

@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label Nov 6, 2025
@ConradIrwin
Copy link
Member

/perf

(Trying out our new perf infrastructure more than anything.)

Are there any potential compatibility concerns with jemalloc? I'm surprised that it's not the default if it's just better

@zed-zippy
Copy link

zed-zippy bot commented Nov 6, 2025

⌛ Started perf run...

@redforks
Copy link
Contributor Author

redforks commented Nov 6, 2025

jemalloc used to be default rust memory allocator before rust 1.32, rust 1.32 changes. rust-analyzer compares different memory allocators

@SomeoneToIgnore
Copy link
Contributor

Maybe also check #7140 (comment) — mimalloc used to actually not retain the memory with use, hence "leaked".

Also, breaking changing the feature from #[cfg(feature = "mimalloc")] to something else — is that needed for something?

@redforks redforks closed this by deleting the head repository Nov 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants