Not only a19 is running very slowly whether after renaming an object, moving it inside a folder, compiling or entering play mode but I also have ridiculously low fps on a project that contains only a few primitives and two scripts, one attached to each primitive and one added to an empty game object.
Take a look:
I dare hoping that the team is working on this problem, too many people are having it. 
Hi, It would be super useful if you could report this issue with the bug reporter and include a simple reproduction case. (Your empty project sounds ideal). That way we have more contextual information about platform and other settings which might impact the performance and we can track investigations and outcomes.
I’m going to do that but I doubt my bug report will have any effect.
I just installed a18 and noticed that an empty project created with it also runs at this awful fps. I’m currently installing a7 (the oldest version available), I’ll test an empty project with it.
Edit: the project created with a7 runs at… ta da! with vsync on:
Shall I join it with the bug report? Yes, I think I shall.
Edit 2: I think the problem I describe here ( 2020.2.0a16 - Objects don't fall smoothly compared to 2020.2.0a15 ) is related to that ridiculous fps; I didn’t check that at the time.
Edit 3: Last test made in a15 this time. The empty project runs 10 times slower with vsync on than the same in a7, which is normal, my screen refreshing at 120 Hz.
All tests made within the last hour, on the same computer under the same OS.
Which ones must I send for comparison with my a19 report? The one made in a15 seems the most logical.
And thank you for trying to help.
A reproduction case on the latest or first to show slowdown is sufficient. (Either A15 or A19 is fine)
State the version where it was faster e.g a7 and we can try the same test there to confirm we can reproduce the same effect.
Include as much info as you can about your software (platform, os version, unity version) and hardware setup (numbr of cores, processor type, etc) as this can be an important factor in performance issues. The bug reporter will try and fill in what it can but the more information we have the better we can react to your specific situation.
And if you post a reference to the bug id here when you’ve raised it and then I can also quickly view it myself while its being initially processed
Thanks
Thanks to you!
After adding an fps counter and floating objects to it and building the a19 test project, it appears that it runs at an almost steady 60 fps and the falling objects fall smoothly.
I haven’t reported the problem yet. I found out that there is already a tracker about a very similar problem that is supposed to be fixed in a21: Unity Issue Tracker - [macOS] Editor has very low frame rate in a new project
How long time before a21 is released?
For now, I’m tired of this, I’m rolling back to a15.
I know that the Unity Devs will hate me for this but I will say it anyway.
I really don’t like that the devs are just waiting for us users to prove that there is something wrong - pretty much just waiting for us to send in a repo project. I am not trying to say that the devs are not doing their job, but that there is something fundamentally wrong with the bug-fix cycle.
I’ve sent in some repo cases in the past to fix issues like this before, but every time I do it, I can’t help feeling why nobody in Unity noticed stuff like this before release. I mean, this isn’t happening because it is Alpha, or Beta, it happens everywhere. It is also not like the bugs are a combination of rare cases. Most bugs are pretty much simple things we notice as we turn it on like:
Maybe the devs should really revise the QA process and decrease these obvious issues from happening. To you devs, we might be one of many clients, but to us, Unity is the one engine that we rely on. So please consider it. Thanks
I’m terribly disappointed; it’s still happening in a21. The image below shows the fps in the game view although the vsync is disabled in a completely new and empty project. Enabling vsync doesn’t change a thing:
I’m going to file a bug report; I’ll post its number here.
I don’t see how my hardware could be important since this doesn’t happen in a15 though; this happens from a16 to a21 included.
Here you go!
(Case 1272076)
My bug report was accepted and reproduced in Ubuntu 18.04: Unity Issue Tracker - Linux Editor has low performace in Playmode on a new project
What puzzles me though is that nobody using one of the versions of Unity having this problem under Ubuntu never showed themselves on the forums. Is it that they didn’t notice or is it that nobody uses Unity alpha with Ubuntu? Or do they just complain elsewhere and whine that “Unity is crap”! “… cannot process billions of polygons on screen at an impressive frame rate,!” 
Thanks Unity QA for not dumping my bug report! 
I also get this same bug but as a fellow smelly mint user ;), have to wait and hope someone from the ubuntu master race has the same issue and logs it. Thankfully someone did (1271213). Apparently still not fixed in latest a21 though.
Hi everybody,
Quick update: the issue has been identified and a potential fix is currently being reviewed.
Thank you. Will we get the fix before 2020.2 gets out of alpha?
Probably not - looks like next update is the first beta, going by Known Issues list Unity Editor Alpha Releases
b1 and b2 have both already been cut off and are currently going through internal testing so unfortunately the earliest the fix could land would be b3.
Great, I’m done with alpha testing then.
I hope 2020.3 alpha won’t come with that same problem.
There will be no 2020.3 alpha, only a 2020.3 LTS.
Just a different name for the same thing.
Not really, LTS will normally not get any major new features but an alpha release does.
