From: Peter Schay <pschay@pobox.com>
To: 9fans@cse.psu.edu
Subject: [9fans] env walk optimization
Date: Wed, 9 May 2001 08:30:01 +0000 [thread overview]
Message-ID: <3AF8C3CC.88BBAE0C@pobox.com> (raw)
Hello,
Here's more on the performance subject; I hope the
following optimization is useful and not too inelegant.
The algorithm for walking in #e seems to be O(n*n).
I think it's pretty easy to make it O(n).
For example, on my system the following script takes no
time with 42 environment variables takes 4 seconds with
441 vars:
term% time /fd/0 <<.
#!/bin/rc
rfork e
eval X^(`{seq 1})^('=1')
echo nvars `{ls /env | wc -l}
reply other threads:[~2001-05-09 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AF8C3CC.88BBAE0C@pobox.com \
--to=pschay@pobox.com \
--cc=9fans@cse.psu.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).