1

Quick background, Octave GUI version 6.2.0 takes at least 20-30 seconds to initialize on one computer, but 1-2 seconds on another computer running the same version and same OS. I wanted to figure out where the holdup was, so I used the tic and toc timer functions in various places within the octaverc startup file. At some point, I noticed that merely having tic at the very end of the startup file completely fixed the slow initialize time.

So while my main issue is resolved (though I don't know why that worked), I wanted to see if using tic without ever using toc in an Octave session can cause any issues, e.g., does this leave some timer process running in the background? Thanks in advance.

smcmi
  • 106
  • 8

1 Answers1

2

tic stores the current clock time in an internal variable (see tic_toc_timestamp here, the source code for tic starts right after that line), toc compares the current clock time to the stored variable (see its source code here).

So, no, there’s no timer running in the background after you call tic.

Cris Luengo
  • 55,762
  • 10
  • 62
  • 120
  • I also noticed that while this works when running Octave directly, I have code that opens the Octave GUI and runs a script, all using a batch file, and when I do this, the initialization is still very slow, even with the `tic` command. I followed this instruction: [https://savannah.gnu.org/bugs/?53867] but this didn't help. Are there any other known work-arounds for a slow start-up time for the Octave GUI? – smcmi Feb 21 '22 at 19:13
  • @smcmi I don't know what is causing the slowdown or how to fix it, sorry. – Cris Luengo Feb 21 '22 at 19:30