From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.3 released
Date: Sun, 5 Aug 2012 12:46:52 -0400 [thread overview]
Message-ID: <20120805164652.GJ544@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120806003112.4fd471cd@sibserver.ru>
On Mon, Aug 06, 2012 at 12:31:12AM +0800, orc wrote:
> On Sun, 5 Aug 2012 01:22:20 -0400
> Rich Felker <dalias@aerifal.cx> wrote:
>
> > If I were going to switch to x86_64 cpu, which I will probably do in
> > the next few years, x32 would certainly be appealing. Not decided for
> > sure, but it seems very nice to get all the important benefits of a
> > 64-bit cpu with none of the bloat.
>
> Somewhat bloated, but not so much. Often I see only that massive apps
> like web browsers eat much of RAM usually. 2G usually enough for me to
> run 3-4 qemu-kvm's and bloated Firefox 12 (eats about 700M usually,
> critical was 1G and 100M swap, 1 month of it's uptime). Now I use 4G
> (additional 2G is for tmpfs. I like to store large blobs in /tmp often).
> I use x86_64 for 3 years without any problems. If Firefox (or any
> application of same class, chromium probably) will continue to grow,
> then five or seven years will be enough to make x32 be obsoleted
> (compared with ff3, it's maximum memusage was 300M, and for 3.6 it was
> 400M).
Assuming the market is shifting to battery-powered mobile devices
possibly intended to run for days or even weeks without charging, I
think we're going to start seeing some more efficient apps. I don't
doubt the old behemoths will still be around for a while, but musl is
developed with the assumption/intention that efficiency is going to be
one of the important design criteria for future software. If we were
happy with the level of bloat you're describing above, I think lots of
people in this community would just forget about musl and use glibc...
Rich
next prev parent reply other threads:[~2012-08-05 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 2:36 Rich Felker
2012-08-03 14:01 ` Gregor Richards
2012-08-05 1:00 ` idunham
2012-08-05 3:58 ` John Spencer
2012-08-05 4:56 ` idunham
2012-08-05 5:22 ` Rich Felker
2012-08-05 16:31 ` orc
2012-08-05 16:43 ` orc
2012-08-05 17:05 ` Daniel Cegiełka
2012-08-05 18:29 ` Rich Felker
2012-08-05 16:46 ` Rich Felker [this message]
2012-08-05 17:18 ` orc
2012-08-05 23:39 ` Isaac Dunham
2012-08-05 12:30 ` x32 (was: Re: [musl] musl 0.9.3 released) John Spencer
2012-08-05 12:46 ` Daniel Cegiełka
2012-08-05 12:58 ` Kurt H Maier
2012-08-05 13:15 ` Daniel Cegiełka
2012-08-05 13:32 ` x32 Anthony G. Basile
2012-08-05 14:13 ` x32 Daniel Cegiełka
2012-08-05 13:19 ` x32 Anthony G. Basile
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=20120805164652.GJ544@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).