[Octave-bug-tracker] [bug #53867] Octave startup is extremely slow

[anonymous]

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

No, there is no difference between an interactive session (started from
octave.vbs) and a batch session. There is almost no difference between
octave-cli and octave-gui. When starting the gui, startup is a little bit
slower. The -W flag has no effect. When using the -x option with octave-4.4.0,
the first octave command appears at the screen after about 20 seconds. So the
problem seems to be related to C++ code.


$ time octave-cli-4.2.2 -f --eval "x = pi"
x =  3.1416

real    0m0.296s
user    0m0.000s
sys     0m0.015s



$ time octave-cli-4.4.0 -f --eval "x = pi"
x =  3.1416

real    0m20.441s
user    0m0.000s
sys     0m0.031s


octave-4.2.2

$ time octave-gui.exe --force-gui -f --eval "x = pi"

real    0m0.759s
user    0m0.000s
sys     0m0.031s


octave-4.4.0

$ time octave-gui -f --force-gui --eval "x = pi"

real    0m21.898s
user    0m0.000s
sys     0m0.015s


    _______________________________________________________

Reply to this item at:

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

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