From owner-freebsd-stable@FreeBSD.ORG Mon Dec 12 14:09:32 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 344E0106564A; Mon, 12 Dec 2011 14:09:32 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id E0AC78FC08; Mon, 12 Dec 2011 14:09:31 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Ra6Ed-00011K-IT>; Mon, 12 Dec 2011 14:48:03 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Ra6Ed-0004V9-FJ>; Mon, 12 Dec 2011 14:48:03 +0100 Message-ID: <4EE6060D.5060201@mail.zedat.fu-berlin.de> Date: Mon, 12 Dec 2011 14:47:57 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111109 Thunderbird/8.0 MIME-Version: 1.0 To: Current FreeBSD , freebsd-stable@freebsd.org References: <4EE1EAFE.3070408@m5p.com> <4EE22421.9060707@gmail.com> In-Reply-To: <4EE22421.9060707@gmail.com> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig3C34C0DC945A3DBF809616AD" X-Originating-IP: 130.133.86.198 Cc: freebsd-performance@freebsd.org Subject: Re: SCHED_ULE should not be the default X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 14:09:32 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3C34C0DC945A3DBF809616AD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Not fully right, boinc defaults to run on idprio 31 so this isn't an > issue. And yes, there are cases where SCHED_ULE shows much better > performance then SCHED_4BSD. [...] Do we have any proof at hand for such cases where SCHED_ULE performs much better than SCHED_4BSD? Whenever the subject comes up, it is mentioned, that SCHED_ULE has better performance on boxes with a ncpu > 2. But in the end I see here contradictionary statements. People complain about poor performance (especially in scientific environments), and other give contra not being the case. Within our department, we developed a highly scalable code for planetary science purposes on imagery. It utilizes present GPUs via OpenCL if present. Otherwise it grabs as many cores as it can. By the end of this year I'll get a new desktop box based on Intels new Sandy Bridge-E architecture with plenty of memory. If the colleague who developed the code is willing performing some benchmarks on the same hardware platform, we'll benchmark bot FreeBSD 9.0/10.0 and the most recent Suse. For FreeBSD I intent also to look for performance with both different schedulers available. O. --------------enig3C34C0DC945A3DBF809616AD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAk7mBhMACgkQU6Ni+wtCKv9mzQD9EQm3oYTJl1UY826v0xiOzMeF nrbUBR3bAjsxSp3A2hYA/0TL0ltenxGrjE6h8DEiQg6ozCymbh7vkFCTBnHkZlaP =8zGJ -----END PGP SIGNATURE----- --------------enig3C34C0DC945A3DBF809616AD--