From: haahr@mv.us.adobe.com (Paul Haahr)
To: culliton@srg.srg.af.mil
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Speed of rc
Date: Thu, 8 Apr 1993 11:45:07 -0400 [thread overview]
Message-ID: <9304081545.AA27842@astro.mv.us.adobe.com> (raw)
> When running commands or scripts it seems that rc often takes longer
> than it should, especially compared to sh or ksh.
i don't find this true at all. i haven't ever used ksh seriously, but
rc feels (that's not is, but feels) much faster than sh on all machines
i've tried it on.
> I also seem to
> remember seeing something in comp.unix.shell within the last couple of
> months, about the relative speed of various shells, which showed rc as
> being substantially slower.
i don't remember it that way. as i recall, the numbers from rc looked
about the same as all other shells, which was not surprising, given that
the benchmark seemed to be testing just how fast the machine forked.
> What this leads me to wonder is, if anyone
> has ever bothered to do any serious timing tests or profile rc and find
> out where it's spending its time?
i know that Byron had done this on at least several times during his work
on rc, but i don't think he's done it recently. the last major performance
tweak that i recall was that there were some list operations being done
in O(n^2) time when they didn't have to be, and that fixed, but i'm not
sure if that was a pre- or post-1.4 change.
profiling code & looking for hot spots is always a good thing to do.
i think you'll find that rc is pretty much flat and not spending an
inordinate amount of time in any particular kind of operation.
paul
next reply other threads:[~1993-04-08 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-08 15:45 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-04-15 20:26 speed " Tom Culliton x2278
1993-04-13 20:26 Byron Rakitzis
1993-04-13 21:23 ` John Mackin
1993-04-13 23:42 ` mycroft
1993-04-12 5:51 Speed " Paul Haahr
1993-04-09 15:58 Tom Culliton x2278
1993-04-08 23:09 Paul Haahr
1993-04-08 22:31 Tom Culliton x2278
1993-04-09 0:38 ` Scott Schwartz
1993-04-09 15:23 ` John Mackin
1993-04-13 19:26 ` Chris Siebenmann
1993-04-13 21:13 ` John Mackin
1993-04-09 16:32 ` Dave Mason
1993-04-09 16:39 ` John Mackin
1993-04-09 19:22 ` Dave Mason
1993-04-09 21:12 ` Chris Siebenmann
1993-04-08 20:14 Byron Rakitzis
1993-04-07 19:50 Tom Culliton x2278
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=9304081545.AA27842@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=culliton@srg.srg.af.mil \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).