mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: What's wrong with musl's malloc
Date: Mon, 23 Apr 2018 01:50:47 -0500	[thread overview]
Message-ID: <685ad2c9-61dc-729e-41fc-a0588faddf2a@adelielinux.org> (raw)
In-Reply-To: <20180422193450.GA11638@voyager>


[-- Attachment #1.1: Type: text/plain, Size: 2179 bytes --]

On 04/22/18 14:34, Markus Wichmann wrote:
> Each of these is constant time. I am not sure optimizing fragmentation
> is worth reducing the performance for. Especially in today's desktop
> and server systems, where anything below 16GB of RAM will just get
> laughed off the stage (slight exaggeration).


this is so far off the mark I am actually writing a reply on a Sunday.

FreeBSD is currently discussing optimising NFS to run better on 256 MB
RAM i386 machines, and is considering the case where a non-zero number
of people are running it in 64 MB virtual machines.

Adelie is running KDE Plasma 5 on a Pentium III with 256 MB RAM, with
enough left over for a few tabs in Otter browser.  In fact, our base
specifications for a server install are a 40 MB 486 or better (you can
squeeze text mode much lower, but apk won't run right below 40; our
baseline is 32 MB, however, on the PowerPC).

"Today's" systems fall in to two buckets: computers with insane specs
bought by people in the upper classes, and used computers with lower
specs bought by people in the lower classes.  after spending a
significant chunk of my life (~15 years) in both, I can't see defences
like "anything below 16GB of RAM will get laughed off the stage" as
anything *but* internalised classism.  as engineers, our jobs are to
make software for all people, not for the chosen few that can afford
16GB of RAM.

hell, my new Talos cost me so much that even though I'd technically be
considered upper-class now, I still couldn't afford more than 8 GB RAM
for it in the beginning (I'm planning to upgrade in the next months as
my finances allow).

I'm sorry if this comes off as ranty or preachy.  I'm just trying to
enlighten everyone that 1) not everyone has or *can afford* 16 GB RAM;
2) that's a poor excuse for not tuning software to be the best it can be.

After all, wasted memory is wasted memory, whether you have a lot or a
little.  (Wouldn't you rather fit more photos / videos / text in there
instead of wasting it on malloc overhead?

Best to you and yours,
--arw


-- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-04-23  6:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 20:09 Rich Felker
2018-04-21  5:28 ` Rich Felker
2018-04-21  5:52   ` Rich Felker
2018-04-22 19:34 ` Markus Wichmann
2018-04-23  2:00   ` Rich Felker
2018-04-23 19:02     ` Markus Wichmann
2018-04-23 19:47       ` Rich Felker
2018-04-23  6:50   ` A. Wilcox [this message]
2018-04-23 16:43     ` Rich Felker
2018-04-22 21:40 ` Michael Clark
2018-04-23  2:09   ` Rich Felker
2018-04-23  2:51   ` musl riscv port Rich Felker

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=685ad2c9-61dc-729e-41fc-a0588faddf2a@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.com \
    /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.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).