From: ng0 <contact.ng0@cryptolab.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>, guix-devel@gnu.org
Subject: Re: Adding ‘--enable-openbsd-malloc’ configure-flag to Tor.
Date: Tue, 31 Jan 2017 11:47:11 +0000 [thread overview]
Message-ID: <8760kvfo3k.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <ac4a879a2da404b3f293c79f4cf04bfe@tobias.gr>
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Guix,
>
> On 30/01/17 23:44, Ludovic Courtès wrote:
>> Re: [PATCH] gnu: tor: Add hardening configure-flags.
>>
>> Applied, thanks.
>
> Ah, just too late :-) Although this isn't hardening-related.
>
> I'd like to also add the ‘--enable-openbsd-malloc’ configure flag to our
> Tor <https://www.torproject.org/docs/faq.html.en#RelayMemory>.
>
> Since adding it, I've been able to serve more traffic more reliably on a
> memory-constrained relay — without any noticable increase in load. This
> might be different on a SoC, although I'd suspect RAM would be the
> limiting factor there too.
>
> To anyone willing to give it a try & give their opinion on the matter:
> I'd be very grateful.
>
> Kind regards,
>
> T G-R
>
> PS: Sorry, no patch, because of
>
> --
> Sent from a Web browser. Excuse/enjoy my brevity.
>
The tradeoff is more CPU load. For tor-relays I know how annoying
this can be, but I'm not sure if less RAM, more CPU is a good
idea (or any improvement) for the client-only side.
I need to read more about this and comment again once I know
more.
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-31 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 0:15 Adding ‘--enable-openbsd-malloc’ configure-flag to Tor Tobias Geerinckx-Rice
2017-01-31 11:47 ` ng0 [this message]
2017-01-31 12:07 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760kvfo3k.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).