[Octave-bug-tracker] [bug #61092] Tangible performance degradation on dev between 6th July and 27th of August

[Hendrik K]

Follow-up Comment #5, bug #61092 (project octave):

Additional investigation & checks I did:

I wanted to eliminate build machine issues, so I took a new clean Ubuntu
installation (using a portable USB SSD ubuntu install on my PC) and compiled
octave on this fresh ubuntu image with current dev and July changeset 29857
and run the script bm_61092.m below on the new fresh Ubuntu SSD install with
three octave versions:

a) Current dev
===========
0.1435
1.2833e-03

b) Fresh octave image from June changeset 29857:
===========
0.1407
1.0131e-03 
0.1435/ 0.1407 ~2%
Some small scale degradation but this may be within margin.

c) Existing image I built in July (same changeset 29857) and which still runs
nicely on my machine
=====================
0.1346
1.1270e-03
0.1355/0.1263 ~ 7.2%.

I now think that the additional difference of 5% from (b) to (c) could have
been caused by my build environment at that time which may have been
temporarily and unknowingly to me (by other activities) tuned (CFLAGS?!,static
libraries?, others?) to AMD Ryzen compilation. 

At least this is a reasonable explanation for me why the same source code
produces different performance results on the same HW.  

So I guess that the bug report can be closed.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61092>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/