What I don't understand is: Why do @Peter77 's quarterly performance overview posts seem to come as "new information" to Unity? Shouldn't whatever he's using have long since been integrated into automated nightly tests that help bisect the code and identify the sources of perf. regressions? I assume Unity has tests LIKE this, and maybe what Peter77 is running is catching something they are overlooking, whether it be due to the test environment, or some other factor? Or are the regressions known, and an accepted cost of other improvements or features? I DON'T mean for this post to be a dump on Unity, nor to trivialize what is obviously a very complex problem, I'm just truly confused here and looking to improve my understanding of the situation.