9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: W B Hacker <wbh@conducive.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] slow performance
Date: Sun,  1 Apr 2007 00:55:26 +0800	[thread overview]
Message-ID: <460E927E.4050002@conducive.org> (raw)
In-Reply-To: <e510e47e0703310941l211dddcfo64ca9aa8710081ba@mail.gmail.com>

pedro henrique antunes de oliveira wrote:
> Well, i dont know if this is a plan9 question it self.
> 
> I've writen a program using a data structure and the program spend about 30
> secs to finish the task, some tima later I've compiled the same program
> under other operating system, (and the same computer) and the program 
> finish
> the task with 3 secs.
> 
> 
> anyone knows what can it be?
> 

No definitive answer from me.

But a guess: ISTR seeing that the Plan9 kernel 'lacked a scheduler'.
That can be inconsequential for some situations, very important for others.

That may be stale or even just plain wrong info.

In any case, I'd like to know more myself about the relative effectivness of the 
'native' Plan9 & its kernel vs other 'real', not 'virtual' OS'en.

Being able to 'plumb' and network inherently 'better' is not all that useful if 
a less-elegant OS does better with the BFBI API set.

Any benchmarks (yeah they lie, but ....) around?

Bill




  parent reply	other threads:[~2007-03-31 16:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 16:41 pedro henrique antunes de oliveira
2007-03-31 16:48 ` Lorenzo Fernando Bivens de la Fuente
2007-03-31 16:48 ` Charles Forsyth
2007-03-31 16:57   ` pedro henrique antunes de oliveira
2007-03-31 16:55 ` W B Hacker [this message]
2007-03-31 17:12   ` Uriel
2007-03-31 19:27     ` W B Hacker
2007-03-31 23:20       ` erik quanstrom
2007-03-31 23:35         ` pedro henrique antunes de oliveira
2007-04-01  1:40           ` erik quanstrom
2007-03-31 17:15   ` Charles Forsyth
2007-03-31 18:50 ` Armando Camarero
2007-03-31 21:05   ` C H Forsyth
2007-03-31 23:25     ` pedro henrique antunes de oliveira
2007-04-01  1:32       ` erik quanstrom
2007-04-01  9:22       ` Charles Forsyth
2007-04-01  9:52         ` pedro henrique antunes de oliveira
2007-04-01  9:56           ` pedro henrique antunes de oliveira
2007-04-01 18:24 ` ron minnich
2007-04-01 19:11   ` pedro henrique antunes de oliveira
2007-04-01 19:26     ` geoff
2007-04-01 19:57       ` pedro henrique antunes de oliveira
2007-04-01 20:07         ` Charles Forsyth
2007-04-01 20:11           ` pedro henrique antunes de oliveira
2007-04-01 20:26             ` Charles Forsyth
2007-04-01 21:13             ` ISHWAR RATTAN
2007-04-02  1:52               ` pedro henrique antunes de oliveira
2007-04-01 12:08 erik quanstrom
2007-04-01 12:35 ` pedro henrique antunes de oliveira
2007-04-01 14:39   ` Uriel
2007-04-01 15:11   ` C H Forsyth
2007-04-01 17:35     ` pedro henrique antunes de oliveira
2007-04-01 18:05       ` erik quanstrom
2007-04-02  9:14 phao
2007-04-02  9:31 ` Anselm R. Garbe
2007-04-02  9:38   ` Charles Forsyth
2007-04-02  9:42     ` C H Forsyth
2007-04-02  9:45     ` Anselm R. Garbe
2007-04-02 12:49       ` pedro henrique antunes de oliveira

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=460E927E.4050002@conducive.org \
    --to=wbh@conducive.org \
    --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).