From: William Kenworthy <billk@iinet.net.au>
To: frlinux@gentoo.org
Cc: gentoo-dev ML <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)"
Date: 15 Aug 2003 07:01:15 +0800 [thread overview]
Message-ID: <1060902075.28866.360.camel@rattus.Localdomain> (raw)
In-Reply-To: <1060888932.4387.17.camel@localhost>
I have the uxury of an old cyrix 233 system for testing. Before
prelink, OO took 1 minutes 8 seconds to startup, and afterwards ~45
seconds. Testing was done by doing a clean reboot to eliminate
cacheing, then start OO immediately after loging in. repeat to confirm
it. I then prelinked, rebooted and repeated. Tested for a few weeks to
make sure no problems surfaced, then did two other systems.
I now have 3 systems prelinked (the cyrix, athlon t-bird1.4 with a flaky
abit MB, running at 1.2G, and a dell P4M laptop - all totally stable. 2
are heavily used (the athlon is my home
desktop/firewall/webserver/mail/dns/etc, and the laptop is my work
machine.
Unexpectedly (but I havent measured it), starting OO when a copy is
either running or recently closed, its very noticeably faster than the
same circumstances before prelink - almost stunningly in fact.
You can un-prelink a running system (or problem apps), but I havent
found that neccessary.
BillK
On Fri, 2003-08-15 at 03:22, FRLinux wrote:
> Having read a couple of posts before yours, i'm quite scared to learn
> that prelink could lead to an unstable system. I've never emerged it on
> my gentoo and was considering doing so, anyone could enlighten me on the
> possible risks on this ? I am looking at more stability over speed
> improvements and have been very satisfied with my 1.4rc3 install so far.
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-14 23:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03 ` Sven Vermeulen
2003-08-13 16:15 ` Alan
2003-08-13 20:30 ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12 ` Brad Laue
2003-08-13 14:20 ` Philippe Lafoucrière
2003-08-13 14:25 ` Philippe Lafoucrière
2003-08-13 14:32 ` Chris Gianelloni
2003-08-13 16:17 ` Alan
2003-08-13 16:22 ` Patrick Kursawe
2003-08-13 20:35 ` Chris Gianelloni
2003-08-13 20:32 ` Chris Gianelloni
2003-08-14 10:02 ` Paul de Vrieze
2003-08-13 21:15 ` FRLinux
2003-08-13 22:49 ` William Kenworthy
2003-08-14 2:04 ` Brian Jackson
2003-08-14 10:10 ` Paul de Vrieze
2003-08-14 12:30 ` Chris Gianelloni
2003-08-14 16:59 ` William Kenworthy
2003-08-14 17:38 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01 ` William Kenworthy [this message]
2003-08-13 14:24 ` David Holm
2003-08-13 14:28 ` Philippe Lafoucrière
2003-08-13 16:16 ` Eric Olinger
2003-08-13 19:00 ` Jon Portnoy
2003-08-13 20:02 ` Mike Frysinger
2003-08-14 1:07 ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14 1:13 ` Jon Portnoy
2003-08-14 11:01 ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich
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=1060902075.28866.360.camel@rattus.Localdomain \
--to=billk@iinet.net.au \
--cc=frlinux@gentoo.org \
--cc=gentoo-dev@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