octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52206] semilogy speed


From: Petr Mikulik
Subject: [Octave-bug-tracker] [bug #52206] semilogy speed
Date: Thu, 19 Oct 2017 08:40:46 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Follow-up Comment #2, bug #52206 (project octave):

Hello Rik,

I have updated the table with timings 4.2.1 vs 4.0.3 on various computers. The
slow-down is found on all machines, but it is mostly pronounced on the two
OpenSUSE computers.

(Times are averaged over several measurements rounded to two valid digits.)


32 bit, Ubuntu 16.04, gcc 5.4
4.0     1.1 sec
4.2.1   4.1 sec    => cca 4 times

64 bit, Debian 8, gcc 4.9.2
4.0.3   0.30 sec
4.2.1   1.2 sec   => cca 4 times

64 bit desktop, OpenSUSE 42.2, gcc 4.8.5
4.0.3   0.15 sec
4.2.1   6.1 sec  => cca 40 times
hg      0.83 sec

64 bit notebook, OpenSUSE 42.2, gcc 4.8.5
2.1.73  0.70 sec
3.6.4   2.1 sec
4.0.3   0.53 sec
4.2.1   15 sec  => cca 28 times


I tried to remove $HOME/octave, $HOME/.octaverc, but it did not change
anything.

***

Then I run Octave via
  strace octave-cli test.m 2>log

Comparing the above logs for 4.0.3 and 4.2.1 I can see that 4.2.1 is doing
stat("") such as 
  stat("/opt/octave/octave-4.2.1/ ...")
on every file for all files in /opt/octave/octave-4.2.1/ while 4.0.3 is not
doing that.

***

Further, the log shows that 4.2.1 is 571 times trying to access one font as:

open("/usr/share/fonts/truetype/Roboto-Regular.ttf", O_RDONLY) = 4
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=515100, ...}) = 0
mmap(NULL, 515100, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7f447e973000
close(4)

This font is tried to be open for both gnuplot and qt graphic backends.
This font file exists in /usr/share/fonts/truetype/Roboto-Regular.ttf.
I don't see any place in .octaverc or .config/octave where this font is
mentioned.

***

Can the two above things be the problem?

Petr


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52206>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]