From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ruby-core-bounces@ruby-lang.org>
X-Original-To: poffice@blade.nagaokaut.ac.jp
Delivered-To: poffice@blade.nagaokaut.ac.jp
Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24])
	by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 6E7C41BA007E
	for <poffice@blade.nagaokaut.ac.jp>; Tue,  9 May 2017 14:31:47 +0900 (JST)
Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100])
	by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 4584BB5D8B5
	for <poffice@blade.nagaokaut.ac.jp>; Tue,  9 May 2017 15:15:28 +0900 (JST)
Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75])
	by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id D993418D1D80
	for <poffice@blade.nagaokaut.ac.jp>; Tue,  9 May 2017 15:15:28 +0900 (JST)
Received: from neon.ruby-lang.org (localhost [IPv6:::1])
	by neon.ruby-lang.org (Postfix) with ESMTP id 74D22120756;
	Tue,  9 May 2017 15:15:27 +0900 (JST)
X-Original-To: ruby-core@ruby-lang.org
Delivered-To: ruby-core@ruby-lang.org
Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64])
 by neon.ruby-lang.org (Postfix) with ESMTPS id AE398120718
 for <ruby-core@ruby-lang.org>; Tue,  9 May 2017 15:15:22 +0900 (JST)
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
 by dcvr.yhbt.net (Postfix) with ESMTP id 2EB4B1FF34;
 Tue,  9 May 2017 06:15:20 +0000 (UTC)
Date: Tue, 9 May 2017 06:15:20 +0000
From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Message-ID: <20170509061520.GA8654@starla>
References: <38090d10-c6a1-5097-66af-130275d773ea@atdot.net>
 <2b47c736-08d8-095b-0454-2dd0b1020b03@atdot.net>
 <20170508030120.GB24763@starla>
 <94ca8f9a-7001-12d3-323d-8c5751569c51@atdot.net>
 <20170508063633.GA6821@starla>
 <4a83bbeb-b22b-61ec-a03f-657746843431@atdot.net>
 <20170509033806.GA27973@starla>
 <a1449c89-e1e3-e3e0-b01f-ec419aa2a514@atdot.net>
 <20170509051223.GA31857@whir>
 <d96fc536-1f7e-3d73-e4fe-92eb64722762@atdot.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <d96fc536-1f7e-3d73-e4fe-92eb64722762@atdot.net>
X-ML-Name: ruby-core
X-Mail-Count: 81052
Subject: [ruby-core:81052] Re: [ruby-cvs:65407] normal:r58236 (trunk):
 thread.c: comments on M:N threading [ci skip]
X-BeenThere: ruby-core@ruby-lang.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ruby developers <ruby-core@ruby-lang.org>
List-Id: Ruby developers <ruby-core.ruby-lang.org>
List-Unsubscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
List-Post: <mailto:ruby-core@ruby-lang.org>
List-Help: <mailto:ruby-core-request@ruby-lang.org?subject=help>
List-Subscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/listinfo/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ruby-core-bounces@ruby-lang.org
Sender: "ruby-core" <ruby-core-bounces@ruby-lang.org>

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?