Why does Xojo take 20 min to start up?

  1. 5 months ago

    Peter S

    Dec 15 Calgary, AB

    I have the full MBS plugin suite and a couple my own custom ones. I could understand if xojo took some time the first time around with a new set of plugins (decompress them, etc, etc and write what it needs to cache on a given machine). But waiting 20 min every time?

    The problem is compounded when you write your own plugins: with each iteration, you need to quit xojo and relaunch to reload your new plugin...then wait another 20 min. Am I missing some pref or setting or is this the new norm? What's it doing at every launch that takes so long?

    Peter

  2. I noticed that when I upgraded to Catalina. I might be wrong but it is possible that the slowest is not cause on XOJO end but rather the Gatekeeper checking every single plugins each time you launch Xojo.

  3. Peter S

    Dec 15 Calgary, AB

    I'm running High Sierra on all 3 macs and it's the same on all of them.

  4. Jean-Yves P

    Dec 15 Testers, Xojo Pro Europe (France, Besançon)

    ssd drives or not ?

  5. Peter S

    Dec 15 Calgary, AB

    all SSD, clocked at 430 to 2000 MB/sec

  6. Jean-Yves P

    Dec 15 Testers, Xojo Pro Europe (France, Besançon)

    I don't think you need to have all mbs plugins at the same time ?
    may be you could remove the non needed ones ?
    I also recall people having such slow start with non up-to-date mbs plugins.

  7. Peter S

    Dec 15 Calgary, AB

    That is a good point, and what I used to do with RS. I figured xojo would be optimized and would decompress/cache the plugins just once, and intelligently detect new ones for caching. I guess I was wrong. The thing with MBS is figuring out dependencies is not always intuitive.
    If I'm not doing anything obviously silly that would cause this slowdown, then pruning is the only option.

  8. Christian S

    Dec 16 Testers, Xojo Pro, XDC Speakers, Third Party Store Germany

    For MBS Plugins, please check dependencies on the plugins here:
    https://monkeybreadsoftware.net/plugindeps.shtml

  9. Jeff T

    Dec 16 Midlands of England, Europe

    please check dependencies on the plugins

    Which is a painful and unreliable way to do it, since before you even begin working through that list, you need to look at all the MBS calls you make in your project and try to work out which plugins they come from!

    I usually look in the libs folder of my Windows build to see what is actually 'needed'.
    (Although why I get dlls and libs which refer to Apple systems, in a Windows build, frustrates me.)

  10. Christian S

    Dec 16 Testers, Xojo Pro, XDC Speakers, Third Party Store Germany

    I know the pain of slow plugin loading.
    We have always all plugins in use here. And we restart Xojo frequently every time a plugin changes.

  11. David C

    Dec 16 Testers, Xojo Pro, XDC Speakers Derby, ITM

    It takes me 3 mins 45 secs to start up Xojo on my SSD with every MBS plugin and some others installed. I would like it faster and multi-CPU loading could be the ticket (if feasible).

  12. Bob K

    Dec 16 Testers, Xojo Pro Kansas City

    The problem is that Xojo doesn't use plugins (except for the few DB plugins) and therefor doesn't see the pain many of their users go through with the very slow startup and plugin compile times. It would be great if they practiced what they preach and spawn helper processes to load and compile plugins.

    Anyone have a Feedback report that asks for this?

  13. Steve K

    Dec 16 Testers, Xojo Pro, XDC Speakers The land of Oz

    I would think it would be nice if xojo could generate a preferences file in the plugins folder that contained what plugins were used in the given project so after the first compile only those plugins would load. If you needed to add a plugin you could edit the prefs file.

  14. Christian S

    Dec 16 Testers, Xojo Pro, XDC Speakers, Third Party Store Germany

    Here is one: Feedback Case #47456

  15. Christian S

    Dec 16 Testers, Xojo Pro, XDC Speakers, Third Party Store Germany

    here is an older closed one: Feedback Case #11543

  16. Peter S

    Dec 16 Calgary, AB

    Feedback Case #58415

  17. Kevin G

    Dec 16 Xojo Pro Gatesheed, England

    @Bob K The problem is that Xojo doesn't use plugins (except for the few DB plugins) and therefor doesn't see the pain many of their users go through with the very slow startup and plugin compile times. It would be great if they practiced what they preach and spawn helper processes to load and compile plugins.

    Anyone have a Feedback report that asks for this?

    At some time in the past I ran instruments on Xojo to see what it was doing during startup. From what I saw I got the impression the bottleneck while loading plugins was doing stuff the IDE needed (maybe for auto-complete) rather than actually loading the plugin's executable code. I don't think helper processes would help there but maybe caching of the data in a SQLite database would.
    Faster precompiling of plugins would be most appreciated as compiling all 3 targets for the first time after a plugin change is basically a toilet & tea break.

  18. Norman P

    Dec 16 Testers, Xojo Pro outside LMAO !!!!!!!

    @Kevin G I don't think helper processes would help there but maybe caching of the data in a SQLite database would.

    you'd think
    turns out it wasnt

  19. Paul R

    Dec 18 Xojo Pro Kirkland, WA

    I did timings on my MBP 2013 running macOS Mojave before I moved to my shiny new MBP 16", sadly running Catalina. All timings were faster (not by as much as you'd think or hope) on the 16" MBP, except for the startup, which was three times as long. I'm pretty sure NannyOS is phoning the mothership for each plugin to make sure Tim Cook approves its use.

  20. Gavin S

    Dec 18 Testers, Xojo Pro, Forum Moderators, MVP UK

    @Paul R I did timings on my MBP 2013 running macOS Mojave before I moved to my shiny new MBP 16", sadly running Catalina. All timings were faster (not by as much as you'd think or hope) on the 16" MBP, except for the startup, which was three times as long. I'm pretty sure NannyOS is phoning the mothership for each plugin to make sure Tim Cook approves its use.

    You're pretty sure, huh. Have you downloaded Little Snitch to test your theory?

  21. Newer ›

or Sign Up to reply!