Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

6

Found in

2020.1

2020.1.12f1

2020.2

2021.1

Issue ID

1299702

Regression

No

AssetDatabase.Refresh takes significantly longer after each code change

Asset - Database

-

How to reproduce:
1. Open the attached project (link in the Edit)
2. Make a change in any script and save

Expected results: AssetDatabase.Refresh takes under a second
Actual results: AssetDatabase.Refresh takes around 15s

Reproducible with: 2020.1.12f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1
Couldn't test with: 2018.4.30f1, 2019.4.17f1 (Many many errors when downgrading, sometimes crashes)

  1. Resolution Note (2021.2.X):

    This issue is being closed, and a number of smaller issues will be created.
    This is due to the fact that AssetDatabase.Refresh kicks off a lot of systems, which, when initialized, end up taking time.
    The following Unity specific areas were found to be able to benefit from additional optimizations:

    Total time: 20s
    Editor Compilation: 5.1s
    Reload All User Assemblies: 3.9s
    HDWizard Constructor: 716ms
    WWiseSettings.LoadSettings: 322ms
    AkWiseXMLWatcher: 131ms
    Editor\Utils\VFXResources.cs OnEnable: 406ms
    SetupComponentMenu: Doing multiple unnecessary file reads (335ms)
    Editor\Models\VFXGraph.cs CheckCompilationVersion: 98ms

    AmplifyShaderEditor.TemplatePostProcessor.PostProcessAllAssets -> Fix by upgrading to latest version

    Issues for these will be created shortly.

Comments (4)

  1. KnightWhoSaysNi

    Jul 23, 2021 09:48

    This issue has been present in Unity 2020 and 2021.
    2019 LTS is much much faster still.

    A 10 second "Hold On" is a thing of the past now. I'm lucky if it takes less than 20sec. And sometimes it's well over a minute. In a relatively empty test project I created a C# script and had to wait for more than 90 seconds for Unity to do something. That's all I did, just create a script and I couldn't do anything for a little over a minute and a half.
    And all I ever get from support regarding this issue is "we're aware of it". For 2 years....

  2. Noizedrop

    Mar 10, 2021 17:35

    I can also confirm what Evan-Greenwood was experiencing

  3. Noizedrop

    Mar 10, 2021 17:30

    I have the exact same issue even on tiny projects. It seems to also be related to the startup time of the project where even the tiny ones are stuck on "Importing" for multiple minutes even when there is literally nothing to import.

    this is seriously impacting workflows

  4. Evan-Greenwood

    Feb 17, 2021 21:37

    Even on small projects I'm often told to "Hold On" now for 10 seconds or more when alt-tabbing back to Unity, or sometimes just clicking on something.

    I've tested this in 2020.1.17 ... This wasn't an issue back in Unity 2019 (and my computer didn't get worse)

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.