(Case 1171423) Asset import significantly slower than in Unity 4.6

The provided test project creates 100 text files, triggers AssetDatabase.Refresh() and then outputs how long the AssetDatabase.Refresh call needed.

Here are the test results on my PC:

  • Unity 2019.3.0f5 = 8.12 seconds

  • Unity 2019.3.0a8 = 10.66 seconds

  • Unity 4.6.3f1 = 4.46 seconds

Video

Reproduce

  • Open attached project on a PC similar to the hardware I used to submit the bug-report with
  • Delete all assets in Assets/Files
  • Press from main menu BugReport > Create 100 assets
  • Repeat this in Unity 2019.3 and Unity 4.6

Actual
Unity 2019.3.0a8 takes significantly longer to refresh its AssetDatabase.

Expected
Newer Unity releases should be faster or equally fast as older Unity releases.

9 Likes

Unity QA was able to reproduce the issue. Good job QA, very much appreciated from my side!

6 Likes

Tested this with Unity 2019.3.0f1. It’s still as slow as I described in the first post, not improved yet.

Bug-report updated with this information.

5 Likes

It’s still being investigated:

1 Like

@Unity_Javier sent me an early build of 2019.3.0f4, which comes with various performance improvements. The editor does feel faster than earlier Unity 2019.3 releases, but there are still a few things that should get ironed out.

Unfortunately the asset import performance didn’t improve, it still costs the same amount of time as mentioned in the first post, which is about twice as slow as Unity 4.6.

I tested this with Unity 2019.3.0f5. Import times of the test attached to the bug-report improved about 2s. Down from 10.66s to 8.1s.

However, 2019.3.0f5 continues to be twice as slow as Unity 4.6, so why has the case been marked as fixed?

9 Likes

I can confirm it’s still a problem today

It’s Funny. So it is in their known issues list. for version 2020.1.0a15 but it links to the solved ticket of 2019.3 So there is not way for us to vote on it. since they seem to be referencing an old completed ticket for a reoccurring issue.

1 Like

Having just submitted a bug report on this, I suggest you probably do the same. This issue is still in 2020.1.2f1, and I don’t see a public tracking issue that we can vote for. To be honest I fear that Unity thinks this issue is resolved, even though there are comments everywhere from people saying that it’s still a problem, including me.

1 Like

Same problem here. Very frustrating.

Make sure you submit an issue as well like Peter77 suggested. The above linked issue from Unity (https://issuetracker.unity3d.com/issues/focusing-the-editor-window-causes-noticeable-slowdowns) is closed, even though there’s clearly tons of people on the forums and reddit posting about how there are performance regressions in the latest couple versions (seems since 2019.3 way up to 2020.2.x).

We really need to bring enough attention to this so they at least re-open the closed ticket (or give us a new one) so everyone can vote on it. Or at least get some feedback from Unity acknowledging that they know that this issue exists and is being at least investigated.

I’m not sure if there’s any other way we can help, but I’d be very willing to help with anything related to speeding up the editor and development speed. If Unity was an open-source project I’d totally be willing to spend a ton of time working to fix an issue like this, but I guess there’s not much we can do :frowning:

confirmation and logged that build time is 2x slower in 2018.lts than in 4.6.9
2X !
how does it even pass the battery of test

I retested it with Unity 2020.2.0a19, here are the results:

For anyone interested, after some emailing with Unity customer support they opened a new ticket for the performance regression and reproduced it in 2019.4, 2020.1 and 2020.2 (couldn’t do 2018.4 since my submitted project won’t compile there). Here’s a link to the issue Unity Issue Tracker - [Performance]Console Pro in non-collapse mode and with large logs causes Slow asset refresh when modifying any script, 45 second if anyone wants to vote on it :slight_smile:

I’d say that this is super positive, though maybe if you guys notice the issue even in 2018.x you probably might want to submit a reproducible build for that too, so it can be linked to the issue?

2 Likes

Thank you for submitting. Is there a project ZIP file I can download to verify on 2018.4.25f1?

I’m looking at 4-8 hours of importing with my editor tool, and it’s absolutely killing my productivity.

I don’t think you can, especially since I didn’t really strip any of my assets out of the bug report, so it contains a lot of stuff from the asset store you probably shouldn’t be able to just download.

The problem with 2018.4.x in the case of my report is that I use ALINE and a few other things which require 2019.x, so it wouldn’t really help you if you could download it I guess.

1 Like

I’m experiencing this too in 2020.1.3. Is impossible to work like this. I’m seeing things like AssetDatabase.Refresh() every time I save my scripts, and most of the time is around 30 seconds to 1 minute just for saving one line. Entering playmode is sometimes ok, but sometimes also very slow. I’ve already expected 30 seconds just to draw the gui of the inspector for a scriptable object.

2 Likes

Since updating to Unity 2020, I’ve always been experiencing this. Horrendous. It is better now than in was in earlier 2020 version, but still getting 30+ seconds every time I save a script.

SAME PROBLEM HERE :frowning:

I’m glad that 2020.2 is faster, but is it stable enough? Right now I’m loosing too much time with this, but I don’t want to switch to a beta version that fixes this but has a whole deal of new toruble, specially considering is a beta. Isn’t like a patch or something for 2020.1 in the mean time?