From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:81052] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip]
Date: Tue, 9 May 2017 06:15:20 +0000 [thread overview]
Message-ID: <20170509061520.GA8654@starla> (raw)
In-Reply-To: <d96fc536-1f7e-3d73-e4fe-92eb64722762@atdot.net>
SASADA Koichi <ko1@atdot.net> wrote:
> On the other hand, aggressive I/O request can conflict by multi-thread
> app. But current ruby threads don't run in parallel, so that it seems no
> problem (hopefully). It seems can cause problem on parallel running
> Guilds (but not available now).
Yes, it's pointless to have so many epoll|kqueue with GVL.
I think Guilds:(epoll|kqueue):nprocesso s can be 1:1:1
relationship. I think memcached is similar in that way with
threads:event_loops:nprocessors.
nginx and cmogstored both allow using multiple processes for
multiple event loops.
Guild won't get around FD allocation contention in processes,
right? In other words, guilds will still be implemented with
separate native threads in same process, but with separate
objspace?
next prev parent reply other threads:[~2017-05-09 5:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170402011414.AEA9B64CEE@svn.ruby-lang.org>
[not found] ` <8a2b82e3-dc07-1945-55f9-5a474e89130b@ruby-lang.org>
2017-04-02 2:35 ` [ruby-core:80531] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] Eric Wong
2017-04-02 3:05 ` [ruby-core:80532] " SASADA Koichi
2017-04-03 4:42 ` [ruby-core:80540] " Eric Wong
2017-05-08 0:33 ` [ruby-core:81027] " Eric Wong
2017-05-08 1:53 ` [ruby-core:81028] " SASADA Koichi
2017-05-08 2:16 ` [ruby-core:81029] " SASADA Koichi
2017-05-08 3:01 ` [ruby-core:81031] " Eric Wong
2017-05-08 3:42 ` [ruby-core:81033] " SASADA Koichi
2017-05-08 6:36 ` [ruby-core:81035] " Eric Wong
2017-05-09 2:18 ` [ruby-core:81042] " SASADA Koichi
2017-05-09 3:38 ` [ruby-core:81044] " Eric Wong
2017-05-09 4:11 ` [ruby-core:81045] " SASADA Koichi
2017-05-09 5:12 ` [ruby-core:81047] " Eric Wong
2017-05-09 5:47 ` [ruby-core:81049] " SASADA Koichi
2017-05-09 6:23 ` [ruby-core:81053] " Eric Wong
2017-05-09 6:44 ` [ruby-core:81054] " SASADA Koichi
2017-05-09 18:51 ` [ruby-core:81078] " Eric Wong
2017-05-10 3:24 ` [ruby-core:81083] " SASADA Koichi
2017-05-10 10:04 ` [ruby-core:81089] " Eric Wong
2017-05-19 4:34 ` [ruby-core:81244] " Eric Wong
2017-06-20 19:16 ` [ruby-core:81733] " Eric Wong
2017-05-09 5:54 ` [ruby-core:81050] " SASADA Koichi
2017-05-09 6:15 ` Eric Wong [this message]
2017-05-08 2:56 ` [ruby-core:81030] " Eric Wong
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170509061520.GA8654@starla \
--to=ruby-core@ruby-lang.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).