tor-webwml.git

@@ -915,9 +915,11 @@ CPU load). You can tell Tor to use this malloc implementation instead:

 <li>If you're running a fast relay, meaning you have many TLS connections

 open, you are probably losing a lot of memory to OpenSSL's internal

-buffers (38KB+ per socket). We've patched OpenSSL to release unused buffer

-memory more aggressively. If you update to OpenSSL 1.0.0-beta5, Tor's

-build process will automatically recognize and use this feature.</li>

+buffers (38KB+ per socket). We've patched OpenSSL to <a

+href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release

+unused buffer memory more aggressively</a>. If you update to OpenSSL

+1.0.0-beta5, Tor's build process will automatically recognize and use

+this feature.</li>

 <li>If you're running on Solaris, OpenBSD, NetBSD, or

 old FreeBSD, Tor is probably forking separate processes