This article is following the function update|memory article and GPU article, to show you more optimization items to improve the experience of browsing the UWA GOT Online Overview report, including the comparative analysis of the Overview report, the number of Batches, function interpretation Tips, etc. These functions can allow you to get started with understanding the report faster, or better integrate into the workflow of the R&D team, forming a more efficient and convenient closed-loop performance data monitoring.
Quickly get the function introduction and optimization suggestions of the past two issues, you can go to:
New features｜Memory article: PSS video memory, memory usage, heap memory object snapshot
function update｜GPU article: SoC GPU information, GPU Counter performance indicators
better comparative analysis
UWA has improved the comparative analysis function of the GOT Online Overview report, and you can quickly enter the "Comparative Analysis" page on the right side of the page.
After selecting the report/scenario, you can view the two tabs of the performance comparison overview and the comparison data table with one click.
Under the performance comparison overview, developers can see a comparison overview of CPU time consumption, GPU time consumption, Jank average, device memory and hardware information, and various important indicators under the five modules.
Under the comparison data table, important indicators such as the reported frame rate, Jank average, and GPU time consumption are displayed by default. In addition, you can also choose to filter custom indicators and add specific parameters for each module as needed.
At the same time, in the table, you can also view the change trends and recommended values of these indicators. For data that exceeds the recommended value, UWA will also highlight the data according to the priority and warning degree of these values.
At the same time, the report also supports export for archiving or further analysis.
By comparing the analysis table, developers can conveniently and fully set up a monitoring process within the team, such as summarizing the performance of the project every two weeks. If the changing parameters are within a reasonable range, continue development. Quick review and rectification.
Add the number of Batches
Under the rendering module of the GOT Online Overview report, the number of Batches has been added, which is the number of Batch submissions during the running of the project. For URP projects, UWA generally recommends paying attention to the number of Batches. If the number of Batches of the project is too high, or even always close to the number of DrawCalls, it means that the batching effect of SRP Batcher is not good.
In this case, the developer needs to use the Frame Debugger to check the factors that interrupt the batching, such as whether the Shader does not support the SRP Batcher, the Shader has multiple passes, interspersed, etc. that lead to the failure of the SRP Batcher.
In addition to the number of Batches, the report also shows the number of Batch.DrawStatic, Batch.DrawDynamic, Batch.DrawInstanced, and Shadows.draw. These categories are part of the total number of Batches. If the corresponding batching method is not used in the project, these functions cannot be obtained. Taking Batch.DrawInstanced as an example, the number of Batch.DrawInstanced is 0, indicating that GPU Instancing is not used in these scenarios.
It should be noted that the number of Batches cannot be obtained under Vulkan.
Display of the number of UGUI DrawCall and the number of particle system DrawCall
Under the rendering module of the GOT Online Overview report, Canvas.RenderSubBatch and ParticleSystem.Draw are modified to give priority to displaying the number of function calls. The number of calls of the two functions represents the number of UGUI DrawCalls and the number of particle system DrawCalls respectively. When these two parameters are high, the time-consuming of translucent rendering will increase, and developers need to continue to pay attention.
Function interpretation tips to help you quickly digest the "stack book"
Under the function stack of each module in the Overview report, a new function definition Tips has been added. Combined with rich optimization experience, UWA has marked the common functions in the optimization process. Move the mouse to the "!" on the right side of the function name to view the function's definition, time-consuming source, optimization method and other information.
Generally speaking, there are many performance parameters encountered in the optimization process. With these thoughtful Tips, you can quickly attribute and provide rectification methods to improve the efficiency of optimization.
I hope these new features and optimizations can help you locate performance problems in projects more easily. If you have more needs and suggestions, you are welcome to submit them to UWA. To browse the Demo report, please click:
Project-UWA-Simple optimization, simple optimization
Welcome to UWA official website to download UWA SDK: UWA | Committed to providing project development solutions for game VR and AR applications | Simple optimization, simple optimization | Yuhu Technology