From owner-freebsd-questions@FreeBSD.ORG Wed Nov 12 23:54:50 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A5D8D8; Wed, 12 Nov 2014 23:54:50 +0000 (UTC) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C713D12; Wed, 12 Nov 2014 23:54:50 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id rl12so14283315iec.24 for ; Wed, 12 Nov 2014 15:54:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KzRtcpM+7b7ffsfPRZOtK19WUhlqecrqc34dBk7dMcY=; b=wkfdK+HmxkvTk6d8UBvkVIGh2ifAYCAvOlP4UK9xy2RuPGFNzM13wul+a4kFl7DYd/ Ibk8sQRn9srayj4q51fUyfAOmcrXc965yvkqBgH1C98KQpWYZCSjI8IdlTSogcBJ5vQu 1ZXtKAN43aiRncgWU+eCkIDHQSAmxBQmXlEHRD1o6xkL3KCyiUprWVYk5/qSJxaJYuzV fpPfnzxapyO4frr6wCew2sipohltgC3W1lLY1vAyCCaT7VlKEOLsxo3YdYYG8ggXzGPe KBtdJMhJIuxzhxMj8UfeNcIkmm+4MzXdEheU1KJ1YiZROqRjlbRgF070rqYIgtQ8RYqp bEDA== MIME-Version: 1.0 X-Received: by 10.50.79.135 with SMTP id j7mr43600815igx.14.1415836489371; Wed, 12 Nov 2014 15:54:49 -0800 (PST) Sender: jdavidlists@gmail.com Received: by 10.43.96.202 with HTTP; Wed, 12 Nov 2014 15:54:49 -0800 (PST) In-Reply-To: References: <20141110071353.GO24601@funkthat.com> <20141112084909.GV24601@funkthat.com> Date: Wed, 12 Nov 2014 18:54:49 -0500 X-Google-Sender-Auth: -GfO5ISEUfnIrhtV7HiQ3hKeBy8 Message-ID: Subject: Re: How thread-friendly is kevent? From: J David To: "K. Macy" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2014 23:54:50 -0000 On Wed, Nov 12, 2014 at 5:31 PM, K. Macy wrote: > Well, this was 8 cores with 45 or so processes. Here's the bench test on a 16 (physical) core machine with 24 threads: Server thread ends after 853093 events. Server thread ends after 834169 events. Server thread ends after 826117 events. Server thread ends after 824130 events. Server thread ends after 826998 events. Server thread ends after 838043 events. Server thread ends after 859163 events. Server thread ends after 844742 events. Server thread ends after 821916 events. Server thread ends after 807776 events. Server thread ends after 805819 events. Server thread ends after 840685 events. Server thread ends after 847173 events. Server thread ends after 834560 events. Server thread ends after 833862 events. Server thread ends after 842143 events. Server thread ends after 866425 events. Server thread ends after 813094 events. Server thread ends after 833364 events. Server thread ends after 805277 events. Server thread ends after 816654 events. Server thread ends after 834174 events. Server thread ends after 851322 events. Server thread ends after 839701 events. This particular test is CPU bound, so more threads don't make much sense, but they also don't make much difference as far as balance. The results are equally even with 128 threads, though the time wasted in kqflxw and context switching is *enormously* larger, aptly demonstrating what John-Mark was talking about. So it seems fairly scalable, at least as of 9.3-STABLE. Good work, whoever it was! Thanks!