From: "Don A. Bailey" <donb@capitolhillconsultants.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9grid?
Date: Tue, 23 Oct 2012 18:18:35 -0700 [thread overview]
Message-ID: <CACyAnEnZPuxKoJGLUnrcxBQKLHSFK8P4qGeLBTvvJwsBydv1Aw@mail.gmail.com> (raw)
In-Reply-To: <CAL4LZyi1TxE_GTG9BgQF-SjLiuv60trwq0USDgf6aHO-11+Wow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]
Thankfully, we are very well versed at tuning the Plan 9 kernel. I'll take
your advice and develop the benchmark.
Is your code concealed per work on NxM? Just curious as NxM seems to solve
(in what little I know about it) some of the issues we are trying to solve
with Go+Plan 9.
D
On Tue, Oct 23, 2012 at 6:15 PM, John Floren <john@jfloren.net> wrote:
> On Tue, Oct 23, 2012 at 5:41 PM, Matthew Veety <mveety@gmail.com> wrote:
> > On 10/23/2012 8:11 PM, Don A. Bailey wrote:
> >>
> >> Go embeds parallel/grid functionality now instead of just lightweight
> >> thread execution? Which packages would you point me at?
> >>
> >> Thanks,
> >> D
> >>
> >> On Tue, Oct 23, 2012 at 5:09 PM, ron minnich <rminnich@gmail.com
> >> <mailto:rminnich@gmail.com>> wrote:
> >>
> >> On Tue, Oct 23, 2012 at 1:22 PM, Don A. Bailey
> >> <donb@capitolhillconsultants.com
> >> <mailto:donb@capitolhillconsultants.com>> wrote:
> >>
> >> > I'm interested in the code for managing grid nodes and delegating
> >> tasks.
> >>
> >> Real code? talk to charles.
> >>
> >> Or now that Go works, you could look at some of those packages.
> >>
> >> ron
> >>
> >>
> >>
> >>
> >> --
> >> Don A. Bailey
> >> CEO/Founding Partner
> >> Capitol Hill Consultants LLC
> >> 1-303-947-6557
> >>
> >>
> >
> > I would avoid using Go on Plan 9 right now for anything production
> because
> > it has issues when using many concurrent tcp connections. If you do want
> to
> > use Go, stick with reading and writing files, and let 9P do it's thing.
> >
> > --
> > Veety
> >
> >
>
> Write a basic http server for Plan 9 (in C) and run Apache Benchmark
> against it. Somewhere around 100 concurrent connections, I tend to get
> failure. There's code in /sys/src/9/ip that has a hard limit on the #
> of concurrent connections IIRC.
>
> I'd post the code for the server I wrote, but it was written as part
> of work so I can't. Still, it's not hard to put together a server
> which responds only to a GET.
>
> john
>
>
--
Don A. Bailey
CEO/Founding Partner
Capitol Hill Consultants LLC
1-303-947-6557
[-- Attachment #2: Type: text/html, Size: 3309 bytes --]
next prev parent reply other threads:[~2012-10-24 1:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 4:49 Don A. Bailey
2012-10-23 14:46 ` Anthony Sorace
2012-10-23 20:22 ` Don A. Bailey
2012-10-24 0:09 ` ron minnich
2012-10-24 0:11 ` Don A. Bailey
2012-10-24 0:41 ` Matthew Veety
2012-10-24 0:44 ` Don A. Bailey
2012-10-24 0:51 ` Matthew Veety
2012-10-24 1:15 ` Don A. Bailey
2012-10-24 1:03 ` Kurt H Maier
2012-10-24 1:11 ` Don A. Bailey
2012-10-24 1:26 ` Kurt H Maier
2012-10-24 1:29 ` Don A. Bailey
2012-10-24 1:34 ` erik quanstrom
2012-10-24 1:42 ` Don A. Bailey
2012-10-24 2:41 ` Bakul Shah
2012-10-24 1:58 ` Kurt H Maier
2012-10-24 1:15 ` John Floren
2012-10-24 1:18 ` Don A. Bailey [this message]
2012-10-24 1:31 ` erik quanstrom
2012-10-24 7:30 ` Anthony Martin
2012-10-24 7:46 ` 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=CACyAnEnZPuxKoJGLUnrcxBQKLHSFK8P4qGeLBTvvJwsBydv1Aw@mail.gmail.com \
--to=donb@capitolhillconsultants.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).