From: Scott Schwartz <schwartz@bx.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] ports performance
Date: Thu, 8 Apr 2004 14:51:25 -0400 [thread overview]
Message-ID: <E1BBecX-0000je-00@ella.bx.psu.edu> (raw)
I've noticed that running (the ported version of) ls under OS X (10.2),
it is very very slow. Profiling tools (is gprof+"recompile the world"
all there is? why doesn't everyone have pixie!) didn't reveal much,
but top shows that lookupd is burning lots of cycles. Apparently we're
doing lots of lookups (of passwd entries I guess) that the native version
doesn't do?
Under linux the difference is very much less, but it's there. At first
I attributed it to something minor like bio doing less buffering than
stdio, but maybe that's not the whole story.
next reply other threads:[~2004-04-08 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 18:51 Scott Schwartz [this message]
2004-04-08 18:59 ` rog
2004-04-08 18:57 ` Rob Pike
2004-04-08 19:07 ` Scott Schwartz
2004-04-08 19:28 ` Geoff Collyer
2004-04-08 19:45 ` Russ Cox
2004-04-08 19:51 ` Scott Schwartz
2004-04-08 19:57 ` Russ Cox
2004-04-09 2:32 ` Russ Cox
2004-04-08 19:10 Ben Huntsman
2004-04-08 19:21 ` rog
2004-04-08 19:35 ` a
2004-04-08 19:44 ` Scott Schwartz
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=E1BBecX-0000je-00@ella.bx.psu.edu \
--to=schwartz@bx.psu.edu \
--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).