From: byron@netapp.com (Byron Rakitzis)
To: culliton@srg.srg.af.mil, haahr@mv.us.adobe.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Speed of rc
Date: Thu, 8 Apr 1993 16:14:44 -0400 [thread overview]
Message-ID: <9304082014.AA16814@netapp.netapp.com> (raw)
I seem to remember the "benchmark" posted on c.u.s as being quite
artificial.
That said, I'll tell you what I know about rc's speed: I don't think
you will make rc ever go faster by examining prof output. The fat
just isn't there. The slowest routine is probably yacc, but it's not
even close to the time you spend in Unix system calls.
The problem can be viewed in one of two ways: either (1) rc is
not perl, or (2) Unix is too slow. Take your pick. rc has to go
do fork/exec for a lot of tasks which a featureful shell or
perl might cram in as a builtin.
I agree that the speed at which scripts run is a valid concern,
and all I can say is that I don't have a good answer at this
time. I can't bring myself to buy into the perl philosophy.
next reply other threads:[~1993-04-10 0:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-08 20:14 Byron Rakitzis [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 15:45 Paul Haahr
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=9304082014.AA16814@netapp.netapp.com \
--to=byron@netapp.com \
--cc=culliton@srg.srg.af.mil \
--cc=haahr@mv.us.adobe.com \
--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).