[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-relays] FreeBSD Guard Memory - Best results with mimalloc 3.2.8 MI_SECURE=ON
- To: Tor Relays List <tor-relays@xxxxxxxxxxxxxxxxxxxx>
- Subject: [tor-relays] FreeBSD Guard Memory - Best results with mimalloc 3.2.8 MI_SECURE=ON
- From: Tor at 1AEO via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 06 Nov 2026 04:48:24 +0000
- Cc: Tor at 1AEO <tor@xxxxxxxx>
- Feedback-id: 134967009:user:proton
- List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
- Reply-to: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Hi All,
Published a study of five memory allocator configurations across 32 production Tor relays on FreeBSD 15.0 and 15.1 over 6 month period. First 3 months as guard relays and last 3 months as middle relays.
Custom-built mimalloc 3.2.8 with `-DMI_SECURE=ON` consistently used the least RAM, averaging 1.63 GiB per relay versus 5.75 GiB with default jemalloc 5.3.0—a 71.7% reduction in RSS during the final 30 days of the Guard comparison.
For non-Guards with DirCache 0, all five configurations averaged roughly 586–599 MiB per relay, making stock FreeBSD jemalloc 5.3.0 a practical choice without a custom allocator to maintain.
Attachment:
image.png
Description: PNG image
Attachment:
publickey - tor@1aeo.com - 0x9288289B.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx
