Waleed emailed an interesting question:
I was wondering about speed improvement working with somewhat complex (5,000+ point) replicators/emitters in 3d space. My current loaded i9 iMac doesn’t like them very much, even when Activity Monitor shows Motion not using much beyond a single CPU thread or two and very little GPU.
Testing the performance of specific real-time effects is pretty much impossible. There are too many variables. This is why measuring rendering speeds is much easier; we have more control over the settings.
But, I was curious. How would an Apple silicon system handle multiple particle systems? Changing the size and position of objects, as well as calculating Behaviors, is CPU-based. Changing colors, or other pixel attributes, is GPU-based.
How hard do the CPUs and GPUs work when there are thousands of elements on screen at once? Also, what is the difference between calculating effects in 2D vs. 3D?
My test system is a 2023 M2 Max Mac Studio with 64 GB of RAM, running macOS Ventura 13.5.2.
I created an eight-second, 1920 x 1080 30 fps Motion project:
Total moving elements: 2,208
Total simultaneous behaviors: 8
NOTE: This test isn’t completely accurate in that I’m not compensating for the different “life spans” of the particles. But I used the default settings for all three effects except for boosting the birthrate of falling cubes to 125/second and changing the color of the cubes. You can try this for yourself and measure your results.
The project consistently ran at 30 frames per second (top red arrow).
I measured system performance using Activity Monitor. My M2 Mac Studio has 12 CPU cores, which means that the maximum potential CPU load for this system is 1200%. The CPUs in this example ran at less than 80%.
NOTE: Motion was using 780 MB of RAM for this project.
The CPU load was spread across most of the CPUs and none were very busy.
The GPU load – indicated by the red arrow – was never more than about 40%. The first time I played this, it took one-to-two seconds to get to full speed. After that, all iterations ran at full speed.
SWITCH TO 3D
When I switched this effect to 3D and added a camera with a Sweep behavior, there was no change in CPU or GPU performance. This tells me that Motion is calculating in 3D all the time, just not displaying it.
There is no doubt that we can create effects in Motion that won’t play in real time. But I was impressed that even complex effects with lots of moving elements did not tax this Apple silicon system. At all.
Give this a try for yourself and see what your system can do.
NEW & Updated!
Edit smarter with Larry’s latest training, all available in our store.