From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] grist for the "synchronous vs. asynchronous" mill
Date: Tue, 24 Mar 2009 10:41:43 -0400 [thread overview]
Message-ID: <d62ad189b348c5e18145125af96b9b07@quanstro.net> (raw)
In-Reply-To: <13426df10903240729s41bfc3d8i5bf7d5a436da14f@mail.gmail.com>
> On Tue, Mar 24, 2009 at 6:34 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> > On Tue Mar 24 08:54:12 EDT 2009, rogpeppe@gmail.com wrote:
> >> http://www.classhat.com/tymaPaulMultithread.pdf
> >
> > seems more like grist for the task vs. process
> > debate. not that the outcome is in doubt.
>
> except that they only went to 1000 threads. Once we hit more than
> that, linux fell over badly for us on even a big machine.
i assume it didn't fall over uniformly. what was the weak point?
scheduling?
- erik
next prev parent reply other threads:[~2009-03-24 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 12:51 roger peppe
2009-03-24 13:34 ` erik quanstrom
2009-03-24 14:29 ` ron minnich
2009-03-24 14:41 ` erik quanstrom [this message]
2009-03-28 3:48 ` Roman Shaposhnik
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=d62ad189b348c5e18145125af96b9b07@quanstro.net \
--to=quanstro@quanstro.net \
--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).