On 07/07/11 06:29, Arnaud Lacombe wrote:
On Wed, Jul 6, 2011 at 5:00 PM, Hartmann, O.
On 07/06/11 21:36, Steve Kargl wrote:
On Wed, Jul 06, 2011 at 03:18:35PM -0400, Arnaud Lacombe wrote:
On Wed, Jul 6, 2011 at 12:28 PM, Steve Kargl
On Wed, Jul 06, 2011 at 05:29:24PM +0200, O. Hartmann wrote:
I use SCHED_ULE on all machines, since it is supposed to be performing
better on multicore boxes, but there are lots of suggestions switching
back to the old SCHED_4BSD scheduler.
If you are using MPI in numerical codes, then you want
to use SCHED_4BSD. ?I've posted numerous times about ULE
and its very poor performance when using MPI.
It is rather funny to see that the post you point out has generated
exactly 0 meaningful follow-up then and as you mention later in this
thread, the issue still remains today :-)
Apparently, you are privy to my private email exchanges
I'm also not sure why you're being sarcastic here. The
issue was and AFAIK still is a problem for anyone using
FreeBSD in a HPC cluster. ULE simply performs worse than
Well, I know only very little people using FreeBSD within a HPC cluster or
even for scientific purposes, except myself and some people around here.
Well, quad-core CPU, dual-socket machine are quite common these day,
even in non-HPC system. So, unless you understand enough the issue and
ULE to assert that this issue is tight to this workload only, I would
assume this issue to affect other ULE use-case and a broader user
spectrum than "you and some people around".
Maybe this is a little misunderstanding.
I complained about the fact that FreeBSD is more and more vanishing from
HPC (it was very common in the mid 90s and at the beginning the 2000s).
My former department banned after the introduction of Linux kernel 2.6
all FreeBSD boxes due to a much better performance (network) and the
availability of HPC 64bit compilers. Nevertheless, nowadays the
situation has turned even worse with GPGPU. As you said, multicores are
very common and so the inabilities of the multicore-aware scheduler ULE
become effective not even for a marginal group of users with a specific
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"