July 08 2020
By Rubén Torres Bonet
July 08, 2020
Choose one thing to do at the same time:
Because profiling AND using the editor at the same time will generate hiccups and ruin your profiling session. And you don’t want to start all over again.
So often enough, you just idle in front of the profiler waiting for the moment you wanted to capture all along.
And do not dare touch the editor. Forget about compiling, importing textures or clicking anywhere. That will only bring unpleasant news.
You see, neither waiting nor endless profiling is any fun.
But that no more.
Since Unity 2020.1, you can launch the Unity profiler in standalone mode so you finally can:
Since Unity 2020.1, we now have the option to start the profiler as a standalone process.
This means, the Unity editor and the unity profiler will run in different processes so they don’t block each other. In other words, the OS will give you more mercy.
This is useful for you because running the profiler logic adds considerable overhead to your game session. And that noise isn’t pleasant to hear.
Just think of parsing performance metrics, drawing them and handling the expensive user interaction through charts, tables and filters. Any of that will worsen the performance of the editor and hence of the profiler (and your game, if you’re running it in the editor).
Here are the two biggest benefits of running the unity profiler in standalone mode:
The solution is very simple since Unity 2020.1.
It’s just waiting for you to press the right button.
Launching the profiler in standalone mode is straightforward.
This option is located at Window -> Analysis -> Profiler (Standalone)
Unity will greet you with a nice pop-up to sell you on the benefits of using the standalone unity profiler.
Like the warning says, it will take a few seconds to launch the profiler in standalone mode.
Once the loading completes, you’ll see that the profiler spawns in a completely different window.
And it includes its own console. Yummy!
As much as I’d like to give you more information than that, that’s all about it.
No bells, no whistles.
Everything works as usual and you’re ready to go.
Personally, I avoid using the standalone profiler when possible, mainly because it adds an extra window and it takes longer to load.
However, I found the standalone unity profiler especially useful in two cases:
No matter what, the key is to be aware of the problems caused by running the profile in the same process as the unity editor.
If you need to avoid these performance problems, then running the unity profiler in standalone mode will help you there.
As always, keep this tool in your growing tool shelf and use when it helps.
Yeah, you’ll find more of these neat performance tricks in my Unity Performance Checklist.
Go ahead and grab your copy.