Unity 2018.2.14f1 Static Batching performance issues on Mobile.

Hello, after doing some tests on android on Unity 2018.2.14f1, i noticed that static batching does have much lower performance gain compared to Unity 2017.3.0p1, which seems to be working as it should.

The test scene consists of 1000 spheres with Mobile/Diffuse shader. In 2018.2.14f1 i only get a 7 fps increase, whereas in 2017.3.0p1 the increase is around 20 fps.

Here are screenshots:

Unity 2017.3.0p1 - Static Batching Turned off


Unity 2017.3.0p1 - Static Batching Turned on


Unity 2018.2.14f1 - Static Batching Turned off


Unity 2018.2.14f1 - Static Batching Turned on

 

Hi, i've just updated the screenshots, there was an error with the links, i did not use frame time but the screenshots pretty much explain it all.

 

Each screenshot was taken few seconds after launching the app. I actually waited a few minutes before each test to ensure is not the throttling issue, plus i ran each test quite a lot of times to make sure the results are consistent.

 

It's set Every V Blank. All other setting are identical between the projects as well. I would also like to clarify that the number of the spheres was 2000 instead of the abovementioned 1000.

 

I've just done a similar test on Xperia Z2, and the static batching performance seems to be almost if not identical. I'm not sure but this could very well be a device or GPU/CPU specific issue (Galaxy S8 Exynos).

 

No.

 

4 days ago I've submitted a bug report (Case 1098752), and for some reason it has not appeared on the issue tracker yet.
I've also done a similar test on iPhone X, and I believe it has the same batching issues.

 

BUMP!

 

Have you gotten a reply that they are able to reproduce the issue?

QA may be swamped with bugs these days, they are kinda slow to reply lately (it used to be 1-2 days).

 

Nope, I have not, neither on the FogBugz website nor by email.
it's been over 15 days since it was submitted and the issue still persists.

 

I've just received a message from Unity saying that they've been able to reproduce the bug and have sent it for resolution with their developers.

 

It's been two months and the issue still remains active.
The issue is really affecting many projects and preventing me from using latest Unity features such as SRP, so i was wondering if anybody could vote on this issue so it would get fixed quickly.

https://issuetracker.unity3d.com/is...ching-performance-regression-since-2018-dot-1

 

If you are batching a ton of small things or a lot of the same things, then you may actually find performance to be a lot higher just merging them and not using static batching, in reasonably sized cells. I found significant gains in the past like this for cpu limited devices.

It's because regardless of if it's batched or not, Unity will still be required to handle the memory overhead, processing and of course culling for every individual item in that batch. This isn't cheap under a lot of scenarios.

While this is unrelated to your bug, it may still be worth looking into.