9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port tools speed
Date: Fri, 24 Jul 2009 12:17:47 +0200	[thread overview]
Message-ID: <5d375e920907240317q7fcb306ek6e2b34905e9a93a3@mail.gmail.com> (raw)
In-Reply-To: <80c99e790907240136p46bcf8ebn6232bbd85f25d21c@mail.gmail.com>

My bet is on file system performance. Where did the data come from?

9vx is also much faster, even if binaries are identical, because
fossil is such a dog.

uriel

P.S.: In my experience with werc ( http://werc.cat-v.org ) statically
linking p9p tools further increases performance considerably, p9p
tools are also insanely faster than gnu tools.

On Fri, Jul 24, 2009 at 10:36 AM, Lorenzo Bolla<lbolla@gmail.com> wrote:
> Hi all,
>
> I've just installed the plan9port as described here
> (http://swtch.com/plan9port/man/man1/install.html) on a debian box.
> I was comparing the speed of some commands between the plan9 and the GNU
> version, and I get consistently poorer results for the plan9 ones.
> 'grep' for example, is at least twice as slow as its GNU counterpart.
>
> Moreover, the executables in plan9/bin are bigger. Again, plan9's 'grep' is
> 40% bigger:
> $ ll /bin/grep /usr/local/plan9/bin/grep
> -rwxr-xr-x 1 root root 100500 2009-03-28 22:06 /bin/grep
> -rwxr-xr-x 1 root root 141512 2009-07-24 09:06 /usr/local/plan9/bin/grep
>
> Is it expected? Why? Should I re-compile the plan9port with some
> optimization switches? How?
>
> Thanks!
> L.
>



  parent reply	other threads:[~2009-07-24 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24  8:36 Lorenzo Bolla
2009-07-24  9:08 ` Francisco J Ballesteros
2009-07-24 10:11   ` Rodolfo (kix)
2009-07-24 10:38     ` Lorenzo Bolla
2009-07-24 10:17 ` Uriel [this message]
2009-07-24 10:42   ` Lorenzo Bolla
2009-07-24 13:41 ` erik quanstrom
2009-07-25  9:30   ` Ethan Grammatikidis
2009-07-25 13:40     ` erik quanstrom

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=5d375e920907240317q7fcb306ek6e2b34905e9a93a3@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@9fans.net \
    /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).