Huge spike in the profiler

[covert lark]

Hi, I get many huge spikes in my profiler, with v-sync and without v-sync in the build. And is it normal that the camera is taking up so much time? Also the ui Overlay has only to render 1 thing when it is in range but most of the time this little canvas isnt active.

(Unity 6.3 6000.3.9f1)

[remote sage]

The spikes point to the cpu waiting for gpu on these frames. I'd like to say it's shader compilation, but it seems to happen too often for that. Would it be that you're running something else in parallel that loads the gpu heavily?
Unity does not provide much info on the gpu side of things. Especially not if it's a different app creating the spikes.

As for the cpu render overhead, you have 2 cameras, so it's expect to a degree. Still, 6ms on the main camera is a bit high. How many batches do you have(can you reenable that metric?)?

[covert lark]

Hi, the weird thing is, that it only occurs in the build not in the editor. In die editor the max time in PlayerLoop is 4ms. Not many Batches (172)

[remote sage]

You screenshot is profiling (in) the editor though..?

[covert lark]

Really? the profiler opens when I open my buiild because its a developer build

[covert lark]

this one yes, thats the editor

[remote sage]

OK, then share a screenshot from a build.

[covert lark]

thats from the build

[remote sage]

The statistics also only show the editor side state, so I wouldn't say it's very reliable info.

[remote sage]

Not this. The profiler data like on the screenshot in the first message.

[remote sage]

Also, can you share you project settings - quality tab?

[covert lark]

I tested it with Don't sync in V-sync too but not difference

[remote sage]

This actually shows better performance than in the editor. Not worse.

[remote sage]

And you're testing a windows build, right?

[covert lark]

althoug the cam is using nealy 3x more than in the editor?

[covert lark]

yes

[covert lark]

just to make it clear, every image is from the build expect this one

[remote sage]

The first screen showed ~11ms of time for both cameras. The last on shows ~9.4. 1.5-2ms difference in favor of the build.

I don't see 3x difference anywhere.

[remote sage]

No. The first screenshot of the profiler is not from a build.

[covert lark]

I mean, in the editor PlayerLoop is using less than 4ms

[remote sage]

Then where is this screen from? Because it's definitely not from a build.
https://cdn.discordapp.com/attachments/1489541273651249202/1489541274410160199/Screenshot_2026-04-03_101646.png?ex=69d0caea&is=69cf796a&hm=8ff93b4da9aacfcf35c73baebb5bd7257cd355aa092d645ea366af8865d49f36&

[covert lark]

I know it says Play mode but it reacted to my build

[remote sage]

Okay.

Where do you see the most difference then? Expand the editor capture the same way you expanded the one in the build.

[covert lark]

the Camera is still present but it uses way less and also the uiOverlay is more what I would expect

[remote sage]

Expand the main camera stack a little bit.

In both

[covert lark]

I made it a bit closer so it is esear to read (editor)

[remote sage]

I mean in the build too.

In both(editor and build).

[covert lark]

okay, here is the build

[remote sage]

Hmm... Is that il2cpp build?

[covert lark]

thats what I used, and its mono

[remote sage]

For starters, I'd disable deep profiling support. Then rebuild and test.
If that doesn't make any difference, try il2cpp.

[covert lark]

yo, now it is running with 200-300 FPS +. ❤️ thanks. But do you know why Deep profiling is droping the performance that much?

[remote sage]

Because it's sampling and recording every function timing very deep into the callstack. You'd probably see the same results if you enabled it in the editor(there's deep profiling button at the top).