Strange stats in profiler after 2.6 migration

[Priyank.Jain2]

After we migrated our application to Unigine 2.6.1 from 2.3.1. I am observing performance issues in-general. Our application on some of the low end intel machines (Integrated graphics card generation 7) are impacted majorly. The fps which was ~20(with minimum objects rendered) is now dropped to ~12.

As per Unigine performance profiler

• I can see that "CPU waiting" time is increased in 2.6.1 (from 15ms to 70ms).
• Also one strange behavior is observed for "Interface". Interface is taking more time based on the application launch order. 
  • If I launch 2.3 first than 2.6 time taken by "Interface" is less in 2.3
  • If I launch 2.6 first than 2.3 time taken by "Interface" is less in 2.6
• Also it is observed that ObjectTerrain is somehow participating in "Interface" time (toggling it changes the figures)

Can you help me connecting the dots.

[silent]

Hi Priyank,

It's hard to tell without seeing the exact scene and it's settings. If you can share some test content with us - it would be great (scene build with 2.3.1 and 2.6.1). We can sign NDA if you want, just write to engine-support@unigine.com for that.

If you are getting this numbers from OpenGL - counters can be wrong here - it's better to profile under DX11 - it will correctly show CPU / GPU timings.

Thanks!

[Priyank.Jain2]

We are using OpenGL and cannot switch to DX11 quickly as most of the shaders are still in GLSL. But the problem is performance issue is in OpenGL only( present time numbers could be misleading but we are getting low fps - and when I profiled more its clear that swap time is increased in 2.6). I do not see much difference in present time in DirectX between 2.3 and 2.6.

I will check the possibility of sharing test content.

Edited May 30, 2018 by Priyank.Jain2