Search Issue Tracker

Won't Fix



Found in







Issue ID




[Android][Vulkan] GPU instancing performance loss on some Adreno devices when compared to OpenGLES3



How to reproduce:
1. Open the attached project ""
2. Check if Vulkan is selected as a Graphics API (Edit > Project Settings... > Player)
3. Build and Run the project to an Android device

Expected result: The performance of GPU instancing is the same or better when using Vulkan as a Graphics API instead of OpenGLES3
Actual result: The performance of GPU instancing is significantly worse when using Vulkan as a Graphics API instead of OpenGLES3

Reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.15f1, 2020.2.0b14, 2021.1.0a8

Reproducible on:
VLNQA00052, Xiaomi MI MAX, Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510; OpenGLES3: black screen after splash screen, Vulkan: 2
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530; FPS: OpenGLES3: 15, Vulkan: 9
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540; FPS: OpenGLES3: 20, Vulkan: 7

Not reproducible on:
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76; FPS: 30, Vulkan: 30
VLNQA00339, Lge LG V50 ThinQ 5G (LM-V500N), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640; FPS: 20, Vulkan:18
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72; FPS: 25, Vulkan: 25
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71; FPS: OpenGLES3: 13, Vulkan: 13
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630; FPS: OpenGLES3: 22, Vulkan: 30
35465210338, Samsung Galaxy S10 (SM-G975F), Android 10.0, CPU: Exynos 9820 (ARMv8), GPU: Mali-G76; OpenGLES3: 30, Vulkan: 30

  1. Resolution Note (2021.1.X):

    This issue is caused by too many data being sent to the GPUs inside vertex shader. In the project it was caused by animations of the bones, vertex + bone data on animated objects were causing a bottleneck. Newer versions of Vulkan driver do not have this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.