From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how to use RAM
Date: Tue, 13 Oct 2009 19:58:07 +0200 [thread overview]
Message-ID: <4AD4BFAF.1050800@xunil.at> (raw)
In-Reply-To: <c30988c30910130926p1e1c55a8x69d13f5382a579b2@mail.gmail.com>
Joshua Murphy schrieb:
> Non-ricer? Well... this sorta breaks that category.
;-)
> There's a rather handy tool[1] already in the stage3, I've used it
> alongside bootchart to force-load everything needed into ram during
> boot, before it's needed, so execution gets held up by i/o just a
> little less. Actually shaved a few seconds off of my desktop's bootup
> once upon a time (3.0 GHz core 2 duo on 4GB of ram, which had
> excessive eyecandy while remaining fairly lightweight). The second use
> I put it through, and this one just a little more long-term useful,
> was preloading my wm, most of my home directory (primarily all the
> config files), aterm, firefox, a few other common tools I use, and the
> libraries they were using on my system while logging in. All of my
> applications were starting in no time at all. The catch... I took the
> brute force approach, rather than using an add-on tool to
> automagically choose what to prefetch for me. There are also setting
> in the bootscripts that, if you're not already using them, will make
> use of at least a little, using tmpfs here and there, and also just
> putting /tmp and /var/tmp onto tmpfs (outside of building things like
> open office, this tends to work well). Oh, and if you really do want
> to use up all that ram.... build openoffice in tmpfs... if it could
> use all 8GB for files only, it might actually work out, I know it
> kills off when you only have part of 4GB to feed it.
>
> [1] artifice ~ # busybox readahead
> BusyBox v1.14.2 (2009-10-13 06:37:22) multi-call binary
>
> Usage: readahead [FILE]...
>
> Preload FILE(s) in RAM cache so that subsequent reads for thosefiles
> do not block on disk I/O
I use sys-apps/preload ... is this comparable?
I don't need to speed up boot-times as I use suspend-to-ram on my main
workstation as well, so I don't care much about booting ...
Thanks anyway for sharing! Stefan
next prev parent reply other threads:[~2009-10-13 17:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 20:44 [gentoo-user] how to use RAM Stefan G. Weichinger
2009-10-12 21:52 ` [gentoo-user] " Nikos Chantziaras
2009-10-12 22:01 ` Stefan G. Weichinger
2009-10-12 22:09 ` [gentoo-user] " KH
2009-10-12 22:39 ` Alan McKinnon
2009-10-13 11:35 ` Stefan G. Weichinger
2009-10-12 22:45 ` Dale
2009-10-13 5:56 ` KH
2009-10-13 16:26 ` Joshua Murphy
2009-10-13 17:58 ` Stefan G. Weichinger [this message]
2009-10-14 0:03 ` Joshua Murphy
2009-10-14 7:18 ` Stefan G. Weichinger
2009-10-14 9:42 ` KH
2009-10-14 10:08 ` Stefan G. Weichinger
2009-10-14 10:25 ` Dale
2009-10-14 11:31 ` pk
2009-10-14 11:36 ` Alan McKinnon
2009-10-14 14:33 ` KH
2009-10-14 15:04 ` Dale
2009-10-14 16:55 ` Stefan G. Weichinger
2009-10-14 19:59 ` Alan McKinnon
2009-10-14 20:31 ` Stefan G. Weichinger
2009-10-14 20:21 ` Volker Armin Hemmann
2009-10-14 20:28 ` Stefan G. Weichinger
2009-10-14 20:38 ` Volker Armin Hemmann
2009-10-14 20:43 ` Stefan G. Weichinger
2009-10-14 20:34 ` Alan McKinnon
2009-10-14 20:40 ` Volker Armin Hemmann
2009-10-14 20:40 ` Stefan G. Weichinger
2009-10-14 20:57 ` Alan McKinnon
2009-10-14 20:48 ` Neil Bothwick
2009-10-14 21:01 ` Alan McKinnon
2009-10-15 1:24 ` Stroller
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=4AD4BFAF.1050800@xunil.at \
--to=lists@xunil.at \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox