SRP framerate in editor vs standalone

The frame rate reported in the Editor (stats window) and also the frame rate computed by a custom script is significantly slower than in a standalone build. I am talking 120 fps in Editor and 1000 fps in standalone. Is this a known issue?

 

2018b9:
DoRenderLoop: 44%
EditorOverhead: 25%
Profiler.CollectGlobalStats: 16%

2017.2:
Camera.Render: 68%
Overhead: 7%
Profiler.FinalizeAndSendFrame: 5%

 

It's probably more helpful to have these numbers in absolute milliseconds, since % highly depends on everything else.

 

Anyway, it doesn't really matter. Previously the reported Editor frame rate was highly inaccurate and now with Unity 2018 it is incredibly inaccurate.

 

Only when "maximize on play" is selected, the FPS used to be almost the same as with the standalone when using Unity 2017. But that is not the case anymore either. I will see if I can make a small repo.

 

If you are building for standalone (mac, win, linux), running the game in the editor consumes more resources than running it as a standalone program, which can explain the difference. When e.g. you have the game view panel alongside scene scene panel open in the editor and hit play, your resources must render the game view and the scene view = double effort, since you effectively render the game with at least two cameras ( or even more, depending on your setup). It seems as expected behavior, not a bug.

 

Thanks, I know that. The point is that the difference is way greater with 2018 then with 2017.

 

I see what you mean.
I had a little go with the shaders in the lightweight pipeline, they do not seem so lightweight - 3 passes for the simlpest shader in the shader graph.
Maybe with some examples regarding effective use of the new pipeline we could appreciate its benefits better, right now it seems slow.