Why doesn't Unity use the available resources?

Even running from the editor or from build, I noticed that Unity doesn’t take advantage of a third of the available performance. There is no limitations are set in.
Why not go up the fps when still have plenty of computing power? What could be the problem? Is there a setting I don't know or a technique I should have been paying attention to?

I would be very grateful if someone could help me.

(Sorry for my bad english.)

 

First, the Stats window is not a very reliable measure of performance.

Second - do you have Application.targetFramerate set, or is VSync enabled? What is the refresh rate of your monitor?

 

It's a VR project, so the target framerate 90 fps, but

This is also the case with other monitoring software, not just in the Stats window.

It is a VR project, so the target framerate is 90 fps. But with testing intent, I raised it to 900 to not limit anything. Some test scenes go at 900 fps and use the hardware at 70-80%. I don’t understand what might be limiting the use of resources.
I test it on a monitor because it is not limited. The VR headset runs only at the appropriate fps.
V-sync is off, so it can go above 60 fps.

The 70 fps shown in the picture is a pretty good value, often dropping to 30-40 so that neither the CPU nor the GPU load goes up. They sit there around 30%.

 

Is that CPU measurement from Windows taking into account the multiple cores of your CPU? Maybe just a single core is at 100% utilization, and since Unity is single-threaded unless you are doing something special, that is as fast as it can go.

 

I checked, all the cores are going at pretty much the same performance.

 

Well, the only advice I can give at this point is use the Profiler and try to see what the bottleneck seems to be. That should be step 1 for any performance/framerate issue.

 

Unity has improved its multithreading, but there is still a single main thread. If that main thread gets maxed out, then you're not going above whatever FPS at which that occurs. Also, if you're hitting your specified target frame rate, then it isn't going to go any higher than that because you've specifically told it not to. That's the whole point of setting a target frame rate - you're basically telling Unity to use all the performance necessary to hit that frame rate but do not use any more than that.

If you want better multi core usage than you're seeing, even if you remove any target frame rate, you need to either implement more of your game in your own custom threads yourself, or switch over to the alternative DOTS/ECS system.

 

There's also the Jobs system which supposedly can be used independently of ECS.

 

All CPU Cores are going at pretty much the same load, so there is no maxed core.

As I said before:
"It is a VR project, so the target framerate is 90 fps. But with testing intent, I raised it to 900 to not limit anything. Some test scenes go at 900 fps and use the hardware at 70-80%. I don’t understand what might be limiting the use of resources. I test it on a monitor because it is not limited. The VR headset runs only at the appropriate fps. V-sync is off, so it can go above 60 fps.

The 70 fps shown in the picture is a pretty good value, often dropping to 30-40 so that neither the CPU nor the GPU load goes up. They sit there around 30%."

 

Interestingly: when I turn off dynamic shadows, fps goes up and the load goes down by 5%.
(Fps is still far from the target framerate.)

 

Just another example:


This is the build, and the highest CPU core usage is at 62%, 5 core under 50%, and 3 are between 50% and 60%.
GPU sits at 30-32%.

This game is heavily phisycs based, due to the many cars. The profiler show that the 45% of time is phisycs and there is nothing wrong with it, but why doesn't Unity use the available resources?
I tried everything I could, but nothing helped.

Can anyone help me please?
(Sorry for my bad english.)

 

When I turn off hyper threading on the CPU, the load goes up to 90%. (Fps stays the same.)
So it is likely that hyper threading distorts the measured values.
Thanks to everyone for their help.