Hi Peter,
I have updated regarding the performance degradation after disabling
and re-enabling a core.
It turns out that lu.C.x results show quite big variation and tests
have to be repeated several times and mean value of real time has to
be used to get reliable results.
There is NO regression
Hi Peter,
have you a chance to look into this? Is there anything I can do to
help you to fix it?
Thanks a lot!
Jirka
On Wed, Jun 29, 2016 at 11:58 AM, Peter Zijlstra wrote:
> On Wed, Jun 29, 2016 at 11:47:56AM +0200, Jirka Hladky wrote:
>> Hi Peter,
>>
>> I think Cluster on Die technology was
On Wed, Jun 29, 2016 at 11:47:56AM +0200, Jirka Hladky wrote:
> Hi Peter,
>
> I think Cluster on Die technology was introduced in Haswell generation. The
> server I'm using is equipped with 4x Intel E5-4610 v2 (Ivy Bridge). I have
> double checked the BIOS and there is no cluster on die setting.
On Wed, Jun 29, 2016 at 01:15:17AM +0200, Jirka Hladky wrote:
> Hello,
>
> on NUMA enabled server equipped with 4 Intel E5-4610 v2 CPUs we
> observe following performance degradation:
Do you have cluster on die enabled on that machine? If you disable it,
does it still reproduce?
been disabled and re-enabled
real 2m35.930s
user 148m20.795s
=
Thanks a lot!
Jirka
PS: I have opened this BZ to track this issue
Bug 121121 - Kernel v4.7-rc5 - performance degradation upto 40% after
disabling and re-enabling a core
https://bugzilla.kernel.org/show_bug.cgi?id=121121
reproduce.sh
Description: Bourne shell script
5 matches
Mail list logo
