Startup time #1153
Replies: 9 comments
-
Is that before or after a plugin cache update has been done? Apart from that, I was also thinking the same thing the other day about offloading a few things to threads. |
Beta Was this translation helpful? Give feedback.
-
It's the same on each start, otherwise I would not mention it ;-). |
Beta Was this translation helpful? Give feedback.
-
I think QTractor does not scan plugins or even fill a plugin list until you actually open its plugin dialog. One definite improvement in our long plugin cache scanning, when it happens, |
Beta Was this translation helpful? Give feedback.
-
Isn't QTractor sort of the exception? It's insanely fast at starting...
Did some recordings with a friend that uses Cubase a year ago and I was
actually kind of surprised with how long it took to start, going through
plugins like it was perfectly normal. I would have assumed that would have
been improved by now (though I'm not sure how old that version was).
We can of course aspire to be as fast as QTractor, waiting is annoying.
Though with the cache we've already improved the startup time quite a bit
(and stabilized startup hugely, no more crashes!).
While adding the track menu I came across a comment which hinted that maybe
it should be done in a thread. There are probably a lot of similar stuff
that can be parallellized.
There is still something weird with the cache though I haven't managed to
get to the bottom of it, my recording computer (which has a lot of plugins)
still seems to always refresh the cache. Will get back to you guys on that.
I have a question though regarding LV2, is that handled differently from a
cache perspective? Reading the code (and what is output in the terminal) it
looks like it always goes through the LV2 plugins?
Den fre 14 feb. 2020 kl 00:25 skrev Tim <notifications@github.com>:
… Is that before or after a plugin cache update has been done?
Upon startup, a cache update takes a long time but after that, subsequent
restarts of MusE should
be as fast as they can be (currently).
Are you suffering from repeated slow cache updates on every restart? Let
me know.
Apart from that, I was also thinking the same thing the other day about
offloading a few things to threads.
I can't remember what, not sure if it was startup time...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/orgs/muse-sequencer/teams/musedevteam/discussions/27/comments/1?email_source=notifications&email_token=ABCFAN25NKG575ZPSSDAY5TRCWQO5A5CNFSM4KUYIAG2YY3PNVWWK3TUL52HS4DFWNCGS43DOVZXG2LPNZIG643UKJSXA3DZVJRW63LNMVXHIX3JMTHAAAVUW4>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCFAN4SCJ3AQU5JILGEKVLRCWQO5ANCNFSM4KUYIAGQ>
.
|
Beta Was this translation helpful? Give feedback.
-
Yes. Until last week, I created a cache file for LV2, along with the others, just to 'be thorough'. |
Beta Was this translation helpful? Give feedback.
-
Alright. I suppose that it might be marginally faster to read from the cache, we'll see if there are some drawbacks. Regarding startup speed in general, let me just state that if anyone @kybos? wants to pursue paralleliize the startup - if there is a risk it will affect stability, I'm against. ;) I'm quite happy with how stable MusE is, at least for my workflow, crashes do occur but they are far between. |
Beta Was this translation helpful? Give feedback.
-
Should be no drawbacks, only benefits. Simpler code, no LV2 cache file to worry about, I'm always impressed when I have to wade through QTractor's code. About startup time: I must point out that there is a (slight? not sure) bottleneck in And there's actually a third plugin system involved that I'm trying to merge with all of this: |
Beta Was this translation helpful? Give feedback.
-
I had not intention to do that, it was just an idea, seeing that Tim is improving this area anyway. So I rely on him to do the right thing, sure I'm not going to start modifying the same code in parallel (especially after reading about the three different plugin systems ;-)...).
I have the same experience with the (in)stability of QTractor - that was the reason I started using MusE, after all... |
Beta Was this translation helpful? Give feedback.
-
The older I get, the more skeptic I get ;) |
Beta Was this translation helpful? Give feedback.
-
Please don't stone me if the idea is a complete nonsense... but the start of MusE takes quite long (with default options), about 5 seconds on a high-end machine with 16 cores. Compared with QTractor with less than 0.5 secs... Clearly the initialization of the devices, plugins etc. takes its time, but could not that be done in separate thread(s)? I assume that the availability of the devices is checked by MusE anyway before they are really used...
Beta Was this translation helpful? Give feedback.
All reactions