Profiler in 4.3 vs 4.2

News & General Discussion
1

Either I’m going crazy (usually the case) or now I’m getting needless information from the Profiler when running Development Builds from the iPhone.

In 4.2, Profiler was easy to read and was giving me information regarding performance on the platform…

In 4.3, Profiler is just a giant chunk of red for the Overhead, and tiny lines of meaningless color for my actual app…

As I understand it from various Google search results, Overhead is effectively the Unity Editor, and I’ve made sure to hide and/OR close both the Scene and Game tabs; they are not running. I have no object selected so nothing is running in Inspector. The only thing in the entire editor that is visible is the Profiler and the Console, and then the Hierarchy and the Inspector or Project tabs.

The console reports no Errors, and the usual misc. warnings from 3rd party assets that were there in 4.2

I’ve tried collapsing Unity leaving only the Profiler running on the desktop.

I’ve shutdown and restarted Unity several times.

I’ve rebooted the machine.

Any idea why Profiler was fine in 4.2 and now behaving as such in 4.3?

Thanks guys!

-Steve

2

At the Unite2013 conference, I recall a suggestion being to attach to a deployed process instead of the editor - give that a try and see if it reduces all the noise.

3

Any difference when you toggle deep profiling?

4

Hmmm, not sure I know what you mean. I like the sound of it mind you! …but yea I don’t know what you are referring to. :smile:

…and no Arowx, Deep Profile does nothing differently

Thank you guys

-Steve

EDIT: Oh you’re referring to Xcode…yea I see this but I’m not certain what to attach to (says my app is already being debugged. Do I need to actually shut down Unity?

5

I don’t think Xcode is meant, just a build of your game. Do a build with the ‘Development Build’ and ‘Autoconnect Profiler’ boxes checked, then run the build and watch the profiler.

6

Yea that’s what I’ve been doing (that’s what I meant by Development Build in my first post).

In Xcode there’s an option to Attach to Process under /Debug…but I’ve never used it before so I’m curious what Lypheus is suggesting.

Thanks Superpig!

-Steve

7

In the Profiler there’s a drop down list of available processes to attach to. The Editor is the default one, but if you’re running a debug build on an attached device they should show up in the list too. Make sure that’s what you’re profiling, and not your Editor which is doing nothing (which would explain why it’s all overhead).

8

Yup definitely ‘Active Profile/iPhone’, not the Editor. That was the first thing I checked! :smile:

-Steve

9

Jeez I’m an idiot…

…it’s been so long BUT, I didn’t uncheck ‘Others’ in CPU Usage.

All is as it should be now, sorry guys. Perhaps this thread can serve those that have the Overhead issue and aren’t ware you can turn on/off the individual parameters. :smile:

Thank you all!!

-Steve

EDIT: …but it doesn’t remove Overhead from the Overview, so maybe I’m not that much of an idiot (yet)…hmmmm.