Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Apr 2012 18:55:53 +0100
From:      Attilio Rao <attilio@freebsd.org>
To:        Arnaud Lacombe <lacombar@gmail.com>
Cc:        freebsd-performance@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Scheduler + IPC performance on FreeBSD 7.4, 8.2, 9.0 and -CURRENT
Message-ID:  <CAJ-FndAam4mK53sdUx9vB1mUZx8eKZPzd2y_Y-DH8oO0P9=ERA@mail.gmail.com>
In-Reply-To: <CACqU3MV=2Whd2rWgnxzxehiRSqmi03j22U32c0gcvC%2B=zwzGKA@mail.gmail.com>
References:  <CACqU3MXOM1WOPkinxfs2YJmGbgx8-gAmUbK4L3epKPg6OpQXAw@mail.gmail.com> <CAJ-FndDFHaKBPozhkBd6DxGo6F4UCs=9YGg0uMpB_S8iJ8Om0w@mail.gmail.com> <CACqU3MV=2Whd2rWgnxzxehiRSqmi03j22U32c0gcvC%2B=zwzGKA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Il 06 aprile 2012 18:54, Arnaud Lacombe <lacombar@gmail.com> ha scritto:
> Hi,
>
> On Fri, Apr 6, 2012 at 10:58 AM, Attilio Rao <attilio@freebsd.org> wrote:
>> Il 05 aprile 2012 19:03, Arnaud Lacombe <lacombar@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
>>> =C2=A0- Atom D510, Intel, (incomplete)
>>> =C2=A0- Core 2 Quad Q9560, Intel
>>> =C2=A0- Soekris net5501, AMD (incomplete)
>>> =C2=A0- Xeon E5645, Intel (incomplete)
>>> =C2=A0- Xeon E5620 (dual package), Intel
>>> =C2=A0- Xeon E5-1650 (pending completion)
>>> =C2=A0- Vortex86, DMP
>>>
>>> Tested kernel were:
>>> =C2=A0- FreeBSD 7.4-RELEASE
>>> =C2=A0- FreeBSD 8.2-RELEASE
>>> =C2=A0- FreeBSD 9.0-RC3 and FreeBSD 9.0-RELEASE
>>> =C2=A0- 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?

Attilio


--=20
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-FndAam4mK53sdUx9vB1mUZx8eKZPzd2y_Y-DH8oO0P9=ERA>