From owner-freebsd-fs@freebsd.org Wed Dec 30 18:22:13 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CEA6A55C81 for ; Wed, 30 Dec 2015 18:22:13 +0000 (UTC) (envelope-from jkh@ixsystems.com) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 43B1017B5 for ; Wed, 30 Dec 2015 18:22:12 +0000 (UTC) (envelope-from jkh@ixsystems.com) X-ASG-Debug-ID: 1451499731-08ca042abc3ef070001-3nHGF7 Received: from mail.iXsystems.com ([10.2.55.1]) by barracuda.ixsystems.com with ESMTP id 4CsQcsiE2gd6Xtud (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 30 Dec 2015 10:22:11 -0800 (PST) X-Barracuda-Envelope-From: jkh@ixsystems.com X-Barracuda-RBL-Trusted-Forwarder: 10.2.55.1 X-ASG-Whitelist: Client Received: from [10.8.0.42] (unknown [10.8.0.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id C6C6FA2EF8; Wed, 30 Dec 2015 10:22:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1451499730; bh=V0pYgzlJCaMtGdXkFLbD38w6SWdxPlemrvEXxgTqD5I=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=fqK1nPd/KZ1xq5AC73KREOEmr37raCzjyYneQ0zCkk+c1ML8Q6OXkZN0DqR8w0/Bv vEw3YKW93x2dI5OZLwt6xN33xYEHdHWZCzQJhAZbQJ1aDx0zlSOXG9v3MEHuJURKiJ Bowb99cOTFfd201zK3uld1N7q83IXl8mQc8eWXPw= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage From: Hubbard Jordan X-ASG-Orig-Subj: Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage In-Reply-To: <20151230103152.GS13942@ndevos-x240.usersys.redhat.com> Date: Wed, 30 Dec 2015 10:22:07 -0800 Cc: Rick Macklem , freebsd-fs , gluster-devel@gluster.org Content-Transfer-Encoding: quoted-printable Message-Id: <2D8C2729-D556-479B-B4E2-66E1BB222F41@ixsystems.com> References: <571237035.145690509.1451437960464.JavaMail.zimbra@uoguelph.ca> <20151230103152.GS13942@ndevos-x240.usersys.redhat.com> To: Niels de Vos X-Mailer: Apple Mail (2.3112) X-Barracuda-Connect: UNKNOWN[10.2.55.1] X-Barracuda-Start-Time: 1451499731 X-Barracuda-Encrypted: DHE-RSA-CAMELLIA256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2015 18:22:13 -0000 > On Dec 30, 2015, at 2:31 AM, Niels de Vos wrote: >=20 >> I'm guessing that Linux uses the event-epoll stuff instead of = event-poll, >> so it wouldn't exhibit this. Is that correct? >=20 > Well, both. most (if not all) Linux builds will use event-poll. But, > that calls epoll_wait() with a timeout of 1 millisecond as well. >=20 >> Thanks for any information on this, rick >> ps: I am tempted to just crank the timeout of 1msec up to 10 or = 20msec. >=20 > Yes, that is probably what I would do too. And have both poll = functions > use the same timeout, have it defined in libglusterfs/src/event.h. We > could make it a configurable option too, but I do not think it is very > useful to have. I guess this begs the question - what=E2=80=99s the actual purpose of = polling for an event with a 1 millisecond timeout? If it was some sort = of heartbeat check, one might imagine that would be better served by a = timer with nothing close to 1 millisecond as an interval (that would be = one seriously aggressive heartbeat) and if filesystem events are = incoming that glusterfs needs to respond to, why timeout at all? I also have a broader question to go with the specific one: We (at = iXsystems) were attempting to engage with some of the Red Hat folks back = when the FreeBSD port was first done, in the hope of getting it more = =E2=80=9Cofficially supported=E2=80=9D for FreeBSD and perhaps even = donating some more serious stress-testing and integration work for it, = but when those Red Hat folks moved on we lost continuity and the effort = stalled. Who at Red Hat would / could we work with in getting this back = on track? We=E2=80=99d like to integrate glusterfs with FreeNAS 10, and = in fact have already done so but it=E2=80=99s still early days and = we=E2=80=99re not even really sure what we have yet. Thanks, - Jordan