On 5/27/24 09:24, Benjamin Wesch wrote:
replying to myself here after realizing that i made this quite complicated, sorry.
it depends what you actually want to measure.
i get similar results when just doing this on macos here:
time /Applications/Pd-0.54-1.app/Contents/Resources/bin/pd -send "pd quit" vs. time /Applications/Pd-0.55-0test2c.app/Contents/Resources/bin/pd -send "pd quit"
which measures the time for the core to start and quit. this is not the same as the time it takes for Pd to startup with a functional GUI. esp. with Pd-0.55 (where the GUI is started late), the numbers you get might significantly differ from what you are experiencing when you start Pd interactively.
here's what i get on my Debian system using hyperfine (which runs the
application multiple times, to cater for disk-caching and whatnot)
| version | flags | time | |---------|--------|---------------------| | 0.54-1 | | 131.7 ms ± 21.8 ms | | 0.54-1 | -nogui | 4.7 ms ± 2.6 ms | | 618b63 | | 38.4 ms ± 3.6 ms | | 618b63 | -nogui | 4.1 ms ± 2.3 ms |
the 0.54-1 version is the one packaged in Debian.
the "618b63" version is current master (slightly after 0.55-0test3), but
i haven't found any significant differences between master,
0.55-0test3 and 0.55-0test2c)
tests are run on a Debian/amd64 system (i7-13700K).
if you want to measure the time until the GUI is fully available, you probably have to use a GUI plugin that quits Pd from the GUI side.
mfdgrasd IOhannes