[Jensson]

I profiled this before and after the change using the same code files, the asset reload time is definitely much slower, and asset reloads also triggers a lot of times unnecessarily, often it reloads assets once when you select the editor window, and then it triggers another reload when you hit play, and then it triggers another reload when you end play, effectively reloading the code three times every time you change anything and test. This doesn't always happen, but it never happened before the change for the same code, maybe you can work around it but it isn't obvious what is causing it. The engine isn't slower, but the editor is much slower.

It might be that this improved some things for larger teams, but for the projects I've worked on it was a huge downgrade. Unity marketing said this change would speed things up for large projects, but for small projects with small assets and mostly code things got much much slower than before, which was my point that when they try to compete with unreal they are making the editor worse for smaller creators.

I'm not the only one experiencing problems, here is a thread:

https://forum.unity.com/threads/assetdatabase-v2-refresh-sig...

Wasn't fixed last time I checked. Might be fixed in some beta release.

[jayd16]

What do you mean by a reload, exactly? If the asset isn't changed it won't be re-imported. If you're seeing erroneous reimports, then that is something you can track explicitly.

If you're talking about code compiles or script reloads, that's not really what the asset database deals with. (Although you can script imports so its not entirely unrelated).

That said, they did a lot of work to allow you to handle larger projects with (albeit manual) incremental compilations with asmdefs and the like.

I'm also pretty sure they also didn't add more code reload points, they just added load bars for when they did the code reloads. If you don't want the code to refresh automatically, you can just turn it off.

[Jensson]

> If you're talking about code compiles or script reloads, that's not really what the asset database deals with.

Editor profiler says the asset database v2's AssetDatabase.Refresh calls a function named roughly ~"reload all assemblies". That happens every time you add an empty line to a default code file and at many other times. This didn't happen before, and that is where it spends most of its time.

> That said, they did a lot of work to allow you to handle larger projects with (albeit manual) incremental compilations with asmdefs and the like.

I haven't been able to work around this with asmdefs, if you use an assembly then changing any file in it trigger the above mentioned code reload.

> I'm also pretty sure they also didn't add more code reload points, they just added load bars for when they did the code reloads.

Editor is unresponsive for longer. I know they added more bars, but it is hard to mistake an edit/play cycle taking a second in 2019.1 and then taking 10 seconds in 2020.3 in the same project.

> If you don't want the code to refresh automatically, you can just turn it off.

I want things to reload automatically, disabling that is not a fix.