Question What's the status on the promised 500ms iteration time?

What I'm seeing across the board is slowdowns in the iteration time.
2023 >> 2022 > 2021 >> 2020.1

My guess is that the engine and editor was turned into a multitude of c# modules using job and burst which in many cases causes much slower startup time.

In any case, it's the wrong direction as it's been going on for years so course correction is needed.

 

Domain Reload is what the most time needs, and since the C# code has grown extremely in the engine in recent years, Domain Reload also needs more and more time. The efforts of unity to improve the iteration time was unfortunately completely eaten up. Without these efforts, it would be much worse now.

I don't think something changes here before Untiy upgrade the .NET runtime in the editor to coreCLR/.NET 7+.

 

Last I checked, compile time was also much slower despite 20 cores. In some cases, change in user code can cascade down to editor or c# engine code recompile.

Which is targeted 2025 if I recall, won't hold breath over this.

AssDefs everywhere somewhat mitigate this degradation in iteration time but let's say I uninstalled 2018 so I'm not tempted to compare how bad it's gotten.

 

I can't validate it right now as I don't have Unity on this machine, but as far as I know the engine/editor c# code isn't included, so it should never be recompiled. Of course, the situation is different with packages/modules.

 

That must be it.

 

Except for a configuration change or a debug/release mode switch, packages should never be recompiled, since they are not dependent on user code. If unity does that though, then I'd like to know why.

 

I don't know exactly how that works but the more packages are installed the slower things get.
Anyways I have a kitchen on fire so I'll get back to it and let the unity devs find cause then hopefully fix them.
That's why we use a ready-made engine after all.

 

For interested people yesterday i came across this twitter thread
This problem seems to be mostly fixed in recent work from @s_schoener



Thread: https://twitter.com/s4schoener/status/1635652604763201536

 

It probably shaves off a couple of second out of 40s which won't bring us back to 2018 levels, but that's not to dismiss his work, without him and others working in editor perfs, we'd be in trouble.

 

Oh my, i did read it wrong.. *facepalm*
Yeah well still thankful, these kind of optimizations are done one by one

 

yeah I remember that... seems like inside joke as they went the complete opposite direction with even longer wait times to do anything and everything.. everything..

package manager lets wait for this to load, cached? nah