From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Dan Maas <dmaas@dcine.com>
Cc: Andreas Schwab <schwab@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] ACPI mentioned on lwn.net/kernel
Date: Sat, 26 Jan 2002 03:45:59 +0000 [thread overview]
Message-ID: <20020126034559.G5730@kushida.apsleyroad.org> (raw)
In-Reply-To: <fa.juevf8v.1u7ubb8@ifi.uio.no> <fa.h3u09pv.1v2k3bm@ifi.uio.no> <037801c1a60e$d897e230$1d01a8c0@allyourbase>
In-Reply-To: <037801c1a60e$d897e230$1d01a8c0@allyourbase>; from dmaas@dcine.com on Fri, Jan 25, 2002 at 09:12:03PM -0500
Dan Maas wrote:
> This may be true for environments where people mostly run a handful of
> monolithic applications (*ahem* windows) but look at typical Linuxy things
> like:
>
> make (compiler, assembler, linker processes...)
> forking servers (Apache 1.x...)
> *./configure scripts* (a big one!!!)
> etc...
>
> Startup cost is likely to be a big factor here...
Btw, a little story about startup times and Linux.
I once wrote a Perl script that needed to know the current directory.
It did:
use POSIX 'getcwd'
getcwd(...)
After a few months, I was annoyed by the slowness of this script
(compared with other scripts) and decided to try speeding it up. It
turns out that the above two lines took about 0.25 of a second, and that
was the dominant running time of the script.
I replaced getcwd() with `/bin/pwd`. Lo! It took about 0.0075 second.
Says very good things about Linux' fork, exec and mmap times, and about
Glibc's dynamic loading time, I think.
-- Jamie
next prev parent reply other threads:[~2002-01-26 3:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.juevf8v.1u7ubb8@ifi.uio.no>
[not found] ` <fa.h3u09pv.1v2k3bm@ifi.uio.no>
2002-01-26 2:12 ` [ACPI] ACPI mentioned on lwn.net/kernel Dan Maas
2002-01-26 3:45 ` Jamie Lokier [this message]
2002-01-26 4:33 ` Alexander Viro
2002-01-26 4:38 ` Andrew Pimlott
2002-01-26 4:59 ` Jamie Lokier
2002-01-26 5:11 ` Jamie Lokier
2002-01-27 23:58 Dieter Nützel
[not found] <200201251550.g0PFoIPa002738@tigger.cs.uni-dortmund.de.suse.lists.linux.kernel>
[not found] ` <200201250802.32508.bodnar42@phalynx.dhs.org.suse.lists.linux.kernel>
[not found] ` <jeelkes8y5.fsf@sykes.suse.de.suse.lists.linux.kernel>
[not found] ` <a2sv2s$ge3$1@penguin.transmeta.com.suse.lists.linux.kernel>
[not found] ` <20020126034106.F5730@kushida.apsleyroad.org.suse.lists.linux.kernel>
[not found] ` <012d01c1a687$faa11120$0201a8c0@HOMER.suse.lists.linux.kernel>
2002-01-26 22:43 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 15:42 Moore, Robert
2002-01-25 15:50 ` Horst von Brand
2002-01-25 16:02 ` Ryan Cumming
2002-01-25 16:15 ` Andreas Schwab
2002-01-25 20:05 ` Ryan Cumming
2002-01-26 1:00 ` Linus Torvalds
2002-01-26 3:41 ` Jamie Lokier
2002-01-26 16:39 ` Martin Eriksson
2002-01-26 16:47 ` Jeff Garzik
2002-01-26 17:48 ` Jamie Lokier
2002-01-26 18:25 ` Martin Eriksson
2002-01-26 21:42 ` Linus Torvalds
2002-01-30 9:22 ` Andrey Panin
[not found] ` <Pine.LNX.4.33.0201291412590.18804-100000@coffee.psychology.mcmaster.ca>
2002-01-30 8:00 ` Andrey Panin
2002-01-26 17:33 ` Felix von Leitner
2002-01-26 19:40 ` Florian Weimer
2002-01-27 13:56 ` Martin Dalecki
2002-01-25 2:15 Therien, Guy
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=20020126034559.G5730@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=dmaas@dcine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
/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