Aurelien Jarno <aurel...@aurel32.net> writes:

> On Sun, Jun 02, 2013 at 04:53:35PM +0100, Andrew M. Bishop wrote:
>> I have done some more investigation and the cause of the slowdown
>> appears to be this bug-fix to eglibc:
>> 
>> http://sourceware.org/bugzilla/show_bug.cgi?id=13658

>> Other people are reporting the slowdown as well and there is an eglibc
>> bug report:
>> 
>> http://www.sourceware.org/bugzilla/show_bug.cgi?id=14412
>> 
>> No solution seems forthcoming and the bug is only marked as an
>> "enhancement" rather than critical.
>
> The problem is supposed to have been fixed in version 2.18. In practice
> on my machine, I see that with version 2.18 the performances are almost
> back to the 2.17 level, with version 2.19 the performances are slightly 
> above 2.17.
>
> I therefore guess that the problem is fixed and that the bug could be
> closed. Could you please try and confirm?

I have run the same nbench benchmark as before (on the same computer)
with libc6 version 2.18 (Debian package version 2.18-7 to be exact):

TEST                : Iterations/sec.  :
                    :                  :
--------------------:------------------:
NUMERIC SORT        :          1049.2  :
STRING SORT         :          591.44  :
BITFIELD            :      5.3321e+08  :
FP EMULATION        :          200.18  :
FOURIER             :           36286  :
ASSIGNMENT          :          42.186  :
IDEA                :          7965.2  :
HUFFMAN             :          3676.4  :
NEURAL NET          :          54.476  :
LU DECOMPOSITION    :          2053.2  :
==========================ORIGINAL BYTEMARK RESULTS==========================
INTEGER INDEX       : 103.185
FLOATING-POINT INDEX: 72.690
==============================LINUX DATA BELOW===============================
CPU                 : 4 CPU GenuineIntel Intel(R) Core(TM) i3-3110M CPU @ 
2.40GHz 2424MHz
L2 Cache            : 3072 KB
OS                  : Linux 3.14.1-24
C compiler          : gcc version 4.7.3 (Debian 4.7.3-4) 
libc                : 
MEMORY INDEX        : 31.925
INTEGER INDEX       : 21.915
FLOATING-POINT INDEX: 40.317

The results are slightly better than the benchmarks reported in the
original bug report.  The FOURIER result in particular is faster with
libc 2.18 than it was with either 2.13 and 2.17 and by a fairly
significant margin.  This clearly fixes the problem in version 2.17
and in fact improves on the earlier version as well.

-- 
Andrew Bishop


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to