Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Performance drop after upgrading to 2021.2.9

Discussion in 'Addressables' started by luvjungle, Apr 4, 2022.

  1. luvjungle

    luvjungle

    Joined:
    Dec 18, 2017
    Posts:
    56
    Hi all!
    Recently I upgraded my project from 2020.3.6 to 2021.2.9, Addressables version 1.19.19
    My addressables setup is pretty basic: 1 group, couple of small level prefabs, I use InstantiateAsync on Start.
    After Editor upgrade Instantiation takes huge amount of time like 3-4 seconds compared to near instant in 2020.3
    I tried different approaches, like LoadAssetAsync and Instantiate then, tried WaitForCompletion(), tried splitting my group into multiple group, nothing seems to work.
    The one thing that works is Pack Separately but after I do fix duplicate bundle dependency performance drops again.
    Please help.
     
    luvjungle, Apr 4, 2022
    #1

  2. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Same issue here. 1.18.19 does not have performance issues, yet 1.19.19 is super-slow.

    Unity 2021.2.19f1
    Devices tested: Galaxy S21 Ultra, Google Pixel 4a, iPhone 13 Pro Max

    Unity 2020.3.* did not seem to have any problems with Addressables 1.19.*
     
    IgorBoyko, Apr 8, 2022
    #2
    Prodigga likes this.

  3. davidla_unity

    davidla_unity

    Unity Technologies

    Joined:
    Nov 17, 2016
    Posts:
    730
    Hey all, just wanted to post what I know about this issue. It appears that there's some pretty significant performance regressions in the Editor for 2021.2+, from what I understand.

    Igor, it's interesting to me that you say 1.18.19 doesn't have as many issues with performance as 1.19.19 does on that editor version. From what I'm hearing, the Editor performance is mainly affected by shaders and sprites. I can't think of any fixes we've done involving shaders, but I do know we've fixed some bugs with sprites and sprite atlases. It could be that we're hitting something in the Editor in 1.19.19 due to a bug that we fixed.

    There could still be an Addressable issue, I don't want you to think I'm dismissing that possibility. But, the fact you're both using 2021.2 and having these performance issues, and I've just heard about performance problems affecting that editor version, I think that may be the problem.

    If you're able, please report bugs with Unity regarding this. It's already high on that teams priority list, but any additional info could help get the problem resolved faster.
     
    davidla_unity, Apr 12, 2022
    #3
    ImpossibleRobert and IgorBoyko like this.

  4. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Thanks a lot, I have submitted bugreport via Unity's built-in bugreport sender. Repro steps and example project attached.
    Case 1419672
     
    IgorBoyko, Apr 12, 2022
    #4

  5. sunlight1994

    sunlight1994

    Joined:
    Sep 16, 2018
    Posts:
    3
    I also had the same problem today. After updating to the Unity 2021 LTS version, the resource loading is slow. So, after starting the project in Unity 2020 version, I downgraded it to Addressable 1.18.19 and pushed it to Github. After that the problem was solved. I hope you can solve the problem too.
     
    sunlight1994, Apr 13, 2022
    #5

  6. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    As a workaround, you can avoid downgrading to Unity 2020, just downgrade Addressables. Edit Packages/manifest.json file, open project once and then push all the modifications (you'll have 2 files: manifest.json and packages-lock.json)
     
    IgorBoyko, Apr 13, 2022
    #6
    gleamgames likes this.

  7. alesmasiar

    alesmasiar

    Joined:
    Apr 10, 2018
    Posts:
    5
    I also had similar problem after upgrading to LTS 2021.3.0f1 today. Downgrading Addressables to 1.18.19 helped.
     
    alesmasiar, Apr 13, 2022
    #7

  8. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    @davidla_unity, is there any place we can track this issue? As you've mentioned before, it's already high on that teams priority list, but looks like we're lacking some information on whether it's going to be fixed at all, included in next Unity release, or even if it's reproducible by the team. If I can help with anything, please let me know. Thanks.
     
    Last edited: Apr 15, 2022
    IgorBoyko, Apr 15, 2022
    #8
    ImpossibleRobert likes this.

  9. davidla_unity

    davidla_unity

    Unity Technologies

    Joined:
    Nov 17, 2016
    Posts:
    730
    Hey @IgorBoyko so, I looked up that case number you posted and it still appears to be in our QA's triage queue. Once it's triaged, I think an issue is created on the public issue tracker. I'd have to double check that to be sure. I can try and ping that team to get more info, but I'm not sure how much good I'll do. When they're able to get to triage the ticket they should get back to you via email, at the very least. I'll keep an eye on it as best I can
     
    davidla_unity, Apr 21, 2022
    #9
    IgorBoyko likes this.

  10. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Hello and thanks for your reply. I'm checking this thread and the issue daily, no worries :)
     
    IgorBoyko, Apr 22, 2022
    #10

  11. davidla_unity

    davidla_unity

    Unity Technologies

    Joined:
    Nov 17, 2016
    Posts:
    730
    Just an update, we discussed this case today and my team is going to try and get QA eyes on it sooner than later. Nothing super notable, just wanted to post while I was thinking of it.
     
    davidla_unity, Apr 22, 2022
    #11
    apkdev and IgorBoyko like this.

  12. krzychuwr1_unity

    krzychuwr1_unity

    Joined:
    Jul 28, 2019
    Posts:
    3
    I had the same issue, scenes which were loading in ~1-2 seconds started to take about 10 times longer to load with addressables 19.19 compared to 18.19 (in my case it happened after upgrading 2020 LTS to 2021 LTS).

    Device tested: Oculus Quest 2.

    I was able to work around the issue by downgrading addressables to 18.19 while keeping 2021 LTS, seems to be working fine.
     
    krzychuwr1_unity, Apr 23, 2022
    #12
    IgorBoyko likes this.

  13. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    @davidla_unity hey, I'm once again reaching out to you because there seems to be no response whatsoever yet. I would also like to mention that I'm a pro license subscriber and this feels kinda sketchy right now. Case ID is 1419672. If there are any questions related to reproducing the issue, or anything I could help with, please let me know. Thanks a lot.
     
    Last edited: May 4, 2022
    IgorBoyko, May 4, 2022
    #13
    ImpossibleRobert likes this.

  14. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Last edited: May 4, 2022
    IgorBoyko, May 4, 2022
    #14
    alesmasiar likes this.

  15. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Last edited: May 9, 2022
    IgorBoyko, May 9, 2022
    #15
    alesmasiar likes this.

  16. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    The issue has been marked as "Won't fix" because "No fix is planned for this bug". The... what? Our game is completely unusable because of this. Loading times are increased like mad, creating UI is also super-slow.
     
    Last edited: May 25, 2022
    IgorBoyko, May 25, 2022
    #16
    alesmasiar and tazerg like this.

  17. alesmasiar

    alesmasiar

    Joined:
    Apr 10, 2018
    Posts:
    5
    I'm also curious .... how is this bug being dismissed? The loading time of our app literally increased from ~15s to ~60s - that's 4 times longer. If this is not considered a regression, I don't know what is.
     
    alesmasiar, Jun 2, 2022
    #17
    FamishedMammal and IgorBoyko like this.

  18. kahyong_unity

    kahyong_unity

    Unity Technologies

    Joined:
    Jan 17, 2019
    Posts:
    3
    kahyong_unity, Jun 3, 2022
    #18
    alesmasiar and IgorBoyko like this.

  19. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    Thanks a lot for looking into it, I really appreciate it! Great to see that it wasn't actually dismissed and we won't have to downgrade Addressables version each time we update Unity. Thanks again!
     
    IgorBoyko, Jun 3, 2022
    #19

  20. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    I can confirm that the issue seems to be solved now and Addressables loading speed is back to normal. Unity 2021.3.4f1
     
    IgorBoyko, Jun 7, 2022
    #20
    alesmasiar likes this.

  21. FamishedMammal

    FamishedMammal

    Joined:
    Nov 3, 2015
    Posts:
    99
    What addressables version are you using?
     
    FamishedMammal, Jun 7, 2022
    #21

  22. IgorBoyko

    IgorBoyko

    Joined:
    Sep 28, 2020
    Posts:
    81
    1.19.9
     
    IgorBoyko, Jun 7, 2022
    #22

  23. nikita-gurkov

    nikita-gurkov

    Joined:
    Oct 28, 2022
    Posts:
    1
    In Unity 2021.3.11f1 with Addressables 1.19.19 my addressable instantiation time doubles on Android, memory footprint is the same. Downgraded Addressables to 1.18.19 and the issue is gone.
     
    nikita-gurkov, Oct 28, 2022
    #23
    FamishedMammal likes this.

  24. jurjenfutureplay

    jurjenfutureplay

    Joined:
    Mar 28, 2022
    Posts:
    3
    Noticed the same here, 1.19.19 performs the worst, 1.18.19 performs the best, and it seems like that 1.21.1 performs the same as 2020.3 with 1.19.19.
     
    jurjenfutureplay, Nov 18, 2022
    #24