From a30d7f29b3154a2750887446e04bb5dcc024dc30 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Fri, 24 Oct 2025 19:28:34 +0000 Subject: [PATCH] doc: tuning: add note about 64-bit OpenSSL speedup Since switching HTTPS termination to 64-bit, I've noticed a significant CPU usage reduction on public-inbox.org. IMAPS, NNTPS, and POP3S remain 32-bit for the moment since that doesn't go through varnish and I haven't gotten around to dealing with a 64-bit Xapian (or SQLite) install. My current HTTPS setup is: 64-bit PublicInbox::PsgiRproxy -> varnish -> 32-bit PublicInbox::WWW IMAPS, NNTPS, POP3S hit the same 32-bit public-inbox-netd process directly without a caching layer. --- Documentation/public-inbox-tuning.pod | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/public-inbox-tuning.pod b/Documentation/public-inbox-tuning.pod index 3f2c08616..36f17b36f 100644 --- a/Documentation/public-inbox-tuning.pod +++ b/Documentation/public-inbox-tuning.pod @@ -159,9 +159,10 @@ The open file descriptor limit (C, C in L, C in L) may need to be raised to accommodate many concurrent clients. -Transport Layer Security (IMAPS, NNTPS, or via STARTTLS) significantly -increases memory use of client sockets, be sure to account for that in -capacity planning. +Transport Layer Security (HTTPS, IMAPS, NNTPS, or via STARTTLS) +significantly increases memory use of client sockets, be sure to account +for that in capacity planning. Switching L +to a 64-bit userspace reduced libcrypto.so (OpenSSL) CPU use by ~70%. Bursts of small object allocations late in process life contribute to fragmentation of the heap due to arenas (slabs) used internally by Perl. -- 2.47.3