I’m doing some preliminary 2019.3 tests on a very large project in terms of number of individual assets. One of the features we were most excited about was v2 of the AssetDatabase, which was supposed to significantly increase Editor performance for large projects.
After creating two side-by-side versions of our project, one on 2019.2.2 and one on the latest 2019.3 beta release, not only did we not see any gains, but we actually took a ~40% hit in asset database refresh time (2-second average on 2019.2 and 2.8-second average on 2019.3). Please note that these tests were done on a machine with a significantly better SSD than most developers at our company possess, so in actuality these numbers will be several times higher for our average dev. This is a huge concern for us because refreshes are already extremely slow on our project and eat up a lot of productivity.
I’m hoping that someone can help me figure out what’s going on here and whether or not this is something we can get fixed in a later release. I didn’t see anything in the Known Issues list that seemed related to refreshes, which worries me a little bit more than I would be otherwise.
If specifics about our project, such as number of assets and directories (we have a lot of directories) would be helpful, please let me know and I can provide those numbers.
I’d like to say I’m also running into this, but much, much worse. Asset import times that were ~10ms in 2019.2 are now at 500ms, and every single individual model takes at least 13s. Doesn’t seem to be related to asset type at all, and this is on a 2018 MacBook pro w/ solid state drive.
My project has been re-importing now for around 24 hours. It looks like it’s importing all the .fbx files. But what I’m seeing is that every one is taking around 20 seconds. I guess I was hoping it was simply only updating the progress bar title occasionally, and was actually making more progress that what the progress bar seems to be indicating. If this is really only importing 1 item every 20 seconds, then I imagine it will take many days to complete the process. I guess I’ll let it run, but I’m hoping this is a one-time process.
I am running a project in 2020.2.0a13 and it is persisting. This is an issue being seen by a lot of people rendering Unity unusable as reimporting scripts is taking a long long time.
Seeing this issue on 2020.2a15.1993 too a lot, change one character in a script and wait 20 sometimes 30 seconds for an asset database refresh. Almost unusable.
It is currently taking me upwards of 40 minutes to reimport or refresh anything, even just one script. I am struggling through as my game is nearly ready for release, but this is insane.
We just Updated to version 2019.4 and the AssetDatabase.refresh is taking huge chunks of time to finish when I simply add a new line to a script and click back in the editor. Took 32 seconds to finish loading the editor. They said they fixed it in 2019.3 Unity Issue Tracker - [Regression ADB V1-V2] Focusing the Editor Window causes noticeable Slowdowns But immediately in the next minor version people were reporting it again. And even in the 2020 version people are still experiencing the issue.
Update: I found that deleting prefabs means import takes seconds, I wonder if that fixes it for everyone else. Of course, we really need prefabs to work. I know in 2020 they had changes to prefabs but none of the 2020 version have decent prefab importing. 1.5 hours it started taking for my 20ish prefabs, Unity is becoming unusable and Unity are being silent.
I was having very long times, so I went from 2020 back to 2019. It seemed better, but then things slowed down again. 13 seconds to compile my script and 13 more just to start the game. Out of desparation, I rebooted Windows and the times both went from 13 down to 3.
Everybody who still experience significant delays with the latest Unity version (2019.4 LTS, 2020.x), please submit a bug-report as described in this document: Unity QA: Building quality with passion
If we don’t submit those bug-reports, Unity Technologies probably won’t or can’t fix it. I like to think if they don’t have a bug-report, the issue does not exist for them. Posting in this forum thread will not cause the issue to disappear, unfortunately.
It’s important that you report these issues together with a reproduction project if you want them to get fixed. If you don’t do it, it might be a long time until someone else reports them or until Unity Technologies find them.
After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.
Submitted a bug for this a couple of weeks ago (case 1270910). It would be great if we at least got the issue on the issue tracker to be re-opened so people could vote on it. It’s kinda insane that it’s still closed despite there being tons of comments from people saying that the issue is still there. This delay on every single script change is really making Unity annoying to use.
@Peter77 BTW not to nitpick, but if you’re asking others to share their case numbers, why not share your own too?
Hi guys! Here is what I got after reporting this bug
"Hi,
Thank you for contacting Unity about your issue.
The reported problem is not a bug. AssetDatabase.Refresh window is intended to let the user know that Unity did not freeze and is currently working on something (Asset importing, script compilation, etc.). You can read more about Asset Database Refresh window here: Unity - Manual: Refreshing the Asset Database"
I’m seeing this constantly now in 2020.1.6f1 and it’s causing a huge amount of lost time. Just the simplest change will cause Unity to sit idle with AssetDatabase.Refresh showing for 6+ minutes. The only way around it is to restart Unity every 20 minutes or so, and this in itself causes a huge amount of lost productivity.
So I would say don’t give up if the initial response is not what you hoped for. Just the fact that they re-checked the problem and ended up replying they reproduced it and opened a votable issue for it shows it’s not useless to send bug reports
Maybe a question for Unity is if it would help if all of us experiencing the issue would use the iteration profiler (https://github.com/Unity-Technologies/com.unity.editoriterationprofiler) and send the exported profiler data as well? I’m not sure if this information would be useful for them.
I’ve been dealing with this issue for the last few days since I’ve updated from 2019 to 2020.1.9 ; 1 minute to save any script and same to run the game. I always save to Dropbox, so I closed Dropbox to see if there was a difference and it runs now just like before almost instantly. I don’t know if that was the problem but I thought i post it here.
