was curious now and also tested the current master without this single commit. warning dialogs are all gone and measurements look incredible:
Benchmark 1: Pd-0.55.0-maybelessbad.app/Contents/Resources/bin/pd -send "pd quit" Time (mean ± σ): 240.7 ms ± 5.9 ms [User: 17.3 ms, System: 16.2 ms] Range (min … max): 224.7 ms … 246.9 ms 12 runs
so the question now probably is what we're missing without the "bad commit"?
On Sun, Jun 2, 2024 at 12:32 AM Benjamin Wesch benjamin.wesch@gmail.com wrote:
On Sat, Jun 1, 2024 at 11:27 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
if you know how to use
git bisect, you could try to narrow down the commit that introduced the slowdown.this is new to me, i admit - but hoping that i did it correctly, i now get: 2fe920f88abb814fc89719a617ce48d63a3eae3a is the first bad commit
cheers, ben