From: Bengt Kleberg <bengt@softwell.se>
To: haahr@jivetech.com, tjg@star.le.ac.uk
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Dynamically loading readline on demand (was Re: rc futures)
Date: Fri, 14 Jan 2000 06:11:05 -0500 [thread overview]
Message-ID: <200001141109.MAA30516@trillian.softwell.se> (raw)
> From: Paul Haahr <haahr@jivetech.com>
> > Tim Goodwin wrote
> > Here are the results I got on my 200MHz Linux PC (us = microseconds).
> > rc.static 744us
> > rc.rl.static 865us
> > rc.dynamic 1071us
> > rc.rl.dynamic 1442us
> A ~30% performance
> penaly doesn't seem like that much if it's saving enough by sharing the
> library with other clients.
I would disagree here. I start rc scripts from wily all the time. They are really short
and my SS2 needs all the help it can get to make things faster.
Ofcourse, I do not use readline and run the scripts in sequence, so the memory savings would
not be great (or?, what sizes accompany the rc.static, rc.dynamic, xxx)
> bloat in libraries is probably a good thing
Yes, I agree here. But a shell is special, (my usage of rc is special :-) it is started lots of times, finnishes
quickly and is not run many times in parallell.
Best Wishes, Bengt
===============================================================
Everything aforementioned should be regarded as totally private
opinions, and nothing else. bengt@softwell.se
``His great strength is that he is uncompromising. It would make
him physically ill to think of programming in C++.''
next reply other threads:[~2000-01-14 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 11:11 Bengt Kleberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-07 10:38 Bengt Kleberg
1999-12-15 16:32 rc futures Russ Cox
2000-01-05 11:59 ` Dynamically loading readline on demand (was Re: rc futures) Tim Goodwin
2000-01-01 0:22 ` Paul Haahr
2000-01-14 16:26 ` Tim Goodwin
2000-01-14 19:18 ` Paul Haahr
2000-01-13 0:19 ` Jeremy Fitzhardinge
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=200001141109.MAA30516@trillian.softwell.se \
--to=bengt@softwell.se \
--cc=haahr@jivetech.com \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tjg@star.le.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).