I'm watching this Vuo tutorial and the Run seems to happen instantly. Making same comp on my MBP 17" with an SSD/HDD fusion drive it takes about 3-5 seconds for the Window to appear. Any ideas why it's so slow?


Alastair (@usefuldesign), I

smokris's picture
Submitted by

Alastair, I recreated that composition (attached), and ran a few tests on my 2012 MacBook Pro. I used QuickTime Player to capture the screen, then stepped through the frames to determine how long it took between clicking and when the window appeared:

  • Vuo 0.9: 4.50 seconds
  • Vuo 1.0: 1.65 seconds
  • Vuo 1.1: 1.33 seconds

For Vuo 1.0 and 1.1, we made some compilation performance improvements, so that decline in compilation time makes sense. (And we've found more opportunities for improvement, which we'll be doing in forthcoming releases.)

Between 1 and 2 seconds should be typical for Vuo 1.1 on a system with SSD. Compilation is disk-intensive, so the difference may be that I have just an SSD, and you have an SSD/HDD Fusion Drive — perhaps OS X is storing Vuo on the HDD part of your Fusion Drive.

I'm not too familiar with the Fusion Drive technology — does it give you the option to specify what goes on the SSD vs. HDD? If so, these should go on the SSD to maximize compilation performance:

  • Vuo Editor.app
  • /Users/you/Library/Caches/org.vuo
  • /Users/you/Library/Application Support/Vuo
  • /private/tmp

For comparison, I also ran a

smokris's picture
Submitted by

For comparison, I also ran an analogous test of Xcode 6.3 — I created a new Cocoa Application project, then used QuickTime Player to time how long it took between clicking the Run button and when the application window appeared — Xcode took 12 seconds.

Thanks for the insights.

useful design's picture
Submitted by

Thanks for the insights.

Fusion drive is fairly opaque. It shuffles data between the SSD and HDD according to it's own usage algorithms. As far as I'm aware a user can't force files on or off the SSD. Anytime files change i.e. written/appended it seems like they go to the SSD then when reread they often come from the HDD from anecdotal evidence.


For some reason it creates

smokris's picture
Submitted by

For some reason it creates two windows one blank over the other working window. Because it's an image filter protocol?

Yes, the Image Filter protocol creates its own window. Click Edit > Protocols > Image Filter to turn it off, and you'll get just a single window.

(On my system (2012 MacBook Pro with NVIDIA GeForce GT 650M), your composition runs at 60 FPS. There are some graphics performance issues on non-NVIDIA GPUs, which we're planning to address in the upcoming release.)