We would chip away around 15 seconds of startup time each week on the test project and would then verify these changes with 22 real-world projects. “Right away, there were some low-hanging fruit, but also there were a number of situations that required a bit more outside-the-box thinking. They’ve also collaborated on a suite of internal tools that automate the process of gathering metrics on how changes to the Asset Database impact the performance of the Unity Editor. Starting with a synthetic test project of 900,000 assets, Javier Abud and Jonas Drewsen, senior software engineers from the Asset Database team, collaborated on a benchmarking framework that led to a number of optimizations and improvements to Editor startup times.
Since the Asset Database is responsible for a lot of Unity processes during project startup, we wanted to see how impactful it would be to optimize the Asset Database code.
0 kommentar(er)
