Scheduler + IPC performance on FreeBSD 7.4, 8.2,
9.0 and -CURRENT
lacombar at gmail.com
Fri Apr 6 18:04:02 UTC 2012
On Fri, Apr 6, 2012 at 1:55 PM, Attilio Rao <attilio at freebsd.org> wrote:
> Il 06 aprile 2012 18:54, Arnaud Lacombe <lacombar at gmail.com> ha scritto:
>> On Fri, Apr 6, 2012 at 10:58 AM, Attilio Rao <attilio at freebsd.org> wrote:
>>> Il 05 aprile 2012 19:03, Arnaud Lacombe <lacombar at gmail.com> ha scritto:
>>>> Hi folks,
>>>> Over the past months, I ran on a couple of unused box the
>>>> `hackbench'[HACKBENCH] benchmark used by the Linux folks for tracking
>>>> down various kind of regression/improvement. `hackbench' is a
>>>> scheduler + IPC test (socket xor pipe). It creates producers/consumers
>>>> groups and let a variable quantity of small messages flow happily.
>>>> Producers and consumers are either processes xor threads.
>>>> Tested platforms were
>>>> - Atom D510, Intel, (incomplete)
>>>> - Core 2 Quad Q9560, Intel
>>>> - Soekris net5501, AMD (incomplete)
>>>> - Xeon E5645, Intel (incomplete)
>>>> - Xeon E5620 (dual package), Intel
>>>> - Xeon E5-1650 (pending completion)
>>>> - Vortex86, DMP
>>>> Tested kernel were:
>>>> - FreeBSD 7.4-RELEASE
>>>> - FreeBSD 8.2-RELEASE
>>>> - FreeBSD 9.0-RC3 and FreeBSD 9.0-RELEASE
>>>> - FreeBSD 10-CURRENT as of r231573
>>> Which means you run 10-CURRENT with all the kernel debugging options
>>> on and MALLOC_DEBUG on?
>> I already answered that question. Namely:
>> note: rule [I] is alleviated for -CURRENT kernels, which were built
>> with the same alteration made to GENERIC during the CURRENT->RELEASE
>> transition (ie. WITNESS and a couple of other option disabled).
>> this translates into the following patch (for amd64):
> Did you enable MALLOC_PRODUCTION and rebuilt libc?
Userland originates from FreeBSD 7.4-RELEASE and was not changed for
any of the tests, which are exclusively focused on the kernel. Doing
otherwise would mean changing too many variables.
More information about the freebsd-performance