Date: Thu, 15 Dec 2011 17:26:19 +0100 From: Attilio Rao <attilio@freebsd.org> To: Daniel Kalchev <daniel@digsys.bg> Cc: freebsd-stable@freebsd.org Subject: Re: SCHED_ULE should not be the default Message-ID: <CAJ-FndBmQ6LefogN46eha9mz9ui3xXqEB=QV-=92a=S5kv_PBA@mail.gmail.com> In-Reply-To: <4EE7093E.4050006@digsys.bg> References: <4EE1EAFE.3070408@m5p.com> <4EE22421.9060707@gmail.com> <4EE6060D.5060201@mail.zedat.fu-berlin.de> <20111213073615.GA69641@icarus.home.lan> <4EE7093E.4050006@digsys.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/12/13 Daniel Kalchev <daniel@digsys.bg>:
>
>
> On 13.12.11 09:36, Jeremy Chadwick wrote:
>>
>> I personally would find it interesting if someone with a higher-end system
>> (e.g. 2 physical CPUs, with 6 or 8 cores per CPU) was to do the same test
>> (changing -jX to -j{numofcores} of course).
>
>
> Is 4 way 8 core Opteron ok? That is 32 cores, 64GB RAM.
>
> Testing with buildworld in my opinion is not adequate, as it involves way
> too much I/O. Any advice on proper testing methodology?
I'm sure that I/O and pmap subsystem contention (because of
buildworld) and TLB shootdown overhead (because of 32 CPUs) will be so
overwhelming that you are not really going to benchmark the scheduler
activity at all.
However I still don't get what you want to verify exactly?
Thanks,
Attilio
--
Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-FndBmQ6LefogN46eha9mz9ui3xXqEB=QV-=92a=S5kv_PBA>