How to speed up Unity 5.2 again?

Hello everyone!
Is it just me or is Unity 5.2 generally considerably slower than the versions before? I used 5.0 before and the whole Editor has become very unresponsive after the update. I'm seeing the beachball (OSX) regularly, even when just opening an array of about 10 GameObjects in a script component. Updating scripts, importing stuff and opening scenes (after startup), saving scenes and starting the game in the Editor takes about twice as long as before.
Is there some background magic going on that I might not need and may be able to turn off?

Greetings,
Shu

 

Performance testers wanted..

 

Yes, pretty please. This is impossibru to work with fluidly.

 

I am honestly not seeing any worse performance, nor have I seen any beachball.

 

Same here.

--Eric

 

@JasonBricco @Eric5h5 May I ask what machines you are using? I am working on a 2011 MBP, 2,5 GHz i7 quad core, 8GB RAM. Yosemite already hit my machine in terms of performance (especially the Finder is not as responsive as it used to be on 10.7), now Unity is getting slow.

 

Using a newer mac, but I think the main issue seems to be on Mac machines, windows indeed feels faster.
El Capitan is released out beta today, but not sure if this cause more problems for Unity then solve speed.
Will test I guess in due course, but still dont want to upgrade Xcode

 

Apple said El Capitan would be improving performance, but I doubt it will do much on my machine, because Metal is only supported on 2012 or 2013 (not sure) and newer models.

 

I'm using a brand new 2015 MBP.

 

It used to take a few seconds before I saw the project list after launching 5.1, but first launch of 5.2 was blazingly fast for me on El Capitán. Project conversion went by quickly too, and no beachballs so far.

 

The launcher itself is faster for me, too. But that doesn't help that much as long as work in the Editor itself gets stuck all the time. Also, my projects did take some time to convert (about 10-15 minutes for each project at about 400MB project size). I don't know if that's fast or not.

Alright, thanks. I see. This is probably why you don't notice any difference.

After reading some of the other topics though, I didn't have any crashes so far. May it be very slow and inconvenient to work with, at least it seems to be stable on my device.

 

I doubt it has anything to do with hardware, and a 2011 MPB isn't that much slower than a 2015 MPB anyway. If Unity was half as fast like you say it would be noticeable on any hardware. You have something specific going wrong somewhere with your setup; Unity 5.2 is in general faster than 5.0 and 5.1.

--Eric

 

Well, I don't really know what that could be. I will try to work on some different projects and see if this slowdown is project-specific or not. Other than that, I don't know. My MBP does use an HDD, though. I did work on recent machines, too, and I would say they are running Unity about that much faster as it is slower now for me:
Unity 5.2 (my MBP) --2xspeed--> Unity 5.0 (my MBP) --2xspeed--> Unity 5.0 (not my 2014 iMac)
At least that's roughly what I experienced. Of course, sometimes you will have some other software running in the background, which you would have to take into account, but that's my personal average estimate.
Some benchmarks ( https://browser.primatelabs.com/mac-benchmarks ) suggest about 30% higher ratings on a 2014 MBP compared to mine. I have no idea what to make of it, though.

 

The hardware difference between those usually involve HDD vs. SSD, so it's quite a difference. I never let Unity touch a HDD, so that's probably why everything is amazing for me.

 

Everybody at our office is having issues with the speed of 5.2. The Editor seems to be much slower than before, I have also found my build times to iOS have increased significantly. Our build times on Jenkins used to be 25mins on 5.1.3. Our build times now are currently at 1h 48mins on 5.2. We are using a range of MBP 2010-2011, iMacs 2010 - 2015.

 

Same problem here. Unity 5.2 is extremely slow.

 

I will run some tests later that day actually stopping the time, though.
Just to make sure I'm not hallucinating.

 

I made a blank project, created some highpoly objects in it and added some textures.
here are the editor performance comparisons:

Versions:
5.2.0
5.13p2
5.0.1p2

Open projects window:
2 sec, all versions

Open editor:
3 sec
3 sec
1,5 sec

Build project:
37sec + beachball after about 50%
30 sec + beachball at the end
42 sec + frequent beachballs

Import some assets(meshes and textures only), about 150MB: (frequent beachballs on all versions)
11min 40sec
11min 46 sec
11min 32sec

Looks like this is project-specific or a problem with data from older versions? I couldn't say the results are in line with what I experience in my old project at all.

 

I noticed a big slowdown when I upgraded from Unity 4.6 to Unity 5.1.
Except for launching the editor (this is a little faster on U5 than on U4) the compiling scripts times and general editor response (as entering play mode) are much slower with Unity 5.
Is it even worse with U 5.2?

 

I've been doing some testing on compile times for my own projects the past day, and it seems pretty quick. Back in the 4.x days it used to take ages, even for small projects with just a few scripts. One sprawling mess of mine is near instant at the moment (if I change just one script). I don't have anything shader-heavy, though, since I mostly work in 2D at the moment.

 

I don't know about the exact circumstances, but for me, this issue is project-specific. I ran more of my projects from 5.0 and some of them work just fine.
Is there some sort of cache I might want to delete and rebuild? Maybe that could help?
Also, the projects that do work are actually working faster than before, especially updating scripts.

 

The same for android games, fps is lower in 5.2 by 25%!!! On 5.0.3 60 fps on 5.2 30-40fps. I back to 5.0.3.

 

Yeah, my game on Gear VR seems to be running a good 25% slower on 5.2.0 compared to 5.1.3P3. The first couple of levels in my game used to run at 60fps, now I'm getting around 45fps. :|

 

In the editor for me it also runs alot slower on 5.2. haven't tested it in standalone yet. Around 30%, similar to the posters above me.

 

Absolutely no performance problems here, quite the contrary. I am running on a CustoMac (i5 3570K, Gf 760, 8 GB RAM, SSD, OS X.9.x). For me, the Editor got significantly faster with 5.0 compared to 4.6.x, which I expected since the Editor frontend was supposedly re-written for Mac OS X 64 Bit. Now with 5.2.1 Editor startup times, project loading times, Play mode start times, Asset Store download unpacking times, build creation times etc. seem to be the same as in 5.0. As for in-game FPS, things seem pretty much the same to me, but it's hard to say.

If for you people the project overview is too slow, I'd rather blame your internet connection or Unity's servers.

In a recent bughunt I even deployed Unity 5.2 on a 2007 MacBookPro, and considering the hardware Editor performance wasn't that bad.

For Mac users I would recommend the usual. Do a clean install of the OS - why Apple encourages this horrible habbit of non-clean installs is beyond me. Clean your project of temp files and let them rebuild. And there's no excuse anymore to not use an SSD, given how prices have fallen.

Also be sure to free ingame resources: AssetBundle.Unload(),
Resources.UnloadUnusedAssets() etc.

What I do get are specific crashing/freezing bugs + some quirks that were fixed before 5.2, like jumping from Unity to MonoDevelop file lines not working, MonoDevelop hotkeys wrongly assigned etc. Also Enlighten processes seem to be too highly prioritized, they basically block the machine.

 

In order to clarify the difference in the performance results it would be useful to post what is the project size and complexity being tested because it is not the same a 5-10 Gb. project (or bigger) with many third party assets than make the test in an almost empty project with a few cubes.

 

@angel_m
In my case, the projects that were slowed down ranged from about 60 to 290MB.
I was able to resolve most of the problems. However, I don't know how. I tried to reinstall the Editor (this time, using the full installer, not just the Editor itself), I tried to remove some temp files and I restarted the machine.
Initially opening bigger scenes on older projects still takes pretty long, though.

 

Unity editor works fine, but compiled apk games are slower I must test 5.2.1 in this week.

 

I've noticed a loss of FPS, and 5.2.1 seems way crashier than 5.1 did.

 

Please guys, don't mention any specific information of your projects, because it could happen in the worst case that the issues could be resolved like that, either from Unity or maybe someone has a hint. As no one wants that, go on exactly as before, thanks!

 

Unity 5.2.2 is slow as 5.2.0 and 5.2.1. I dont know why... [some animations not plays in 5.2.2] newer unitey with more bugs I dont like it

 

Thanks for not sharing any specific information, as requested!

 

Funny that the profiler is free for everyone and nobody seems to use it.

 

The case is almost every Android build (with certain complexity not only a few boxes spinning) is performing slower in Unity 5.2+. In other posts it is said one of the reasons can be the change in the default texture compression format.

 

The profiler is for analyzing the running game in the editor, right? But, at least for me, the problem is (/was) related to the editor itself, which does not show up in the profiler, right?

After updating to the most current version, though, it feels like it's working quicker again.

Also:

I find it hard to find any specifics when the problem turns up in multiple projects as long as you can't see any potential connection between those projects that might be causing the problem.

 

There is a button called "Profile Editor" in the profiler, very useful to figure out what's going on with the editor.

 

I see! Thanks! I will take a look at that if I run into those slowdowns again.

 

I didn't know the profiler was free nowadays. Heh... thanks.

 

I'm on OSX El Capitan 10.11.1. MBP late 2011 (2.4 quad i7, 16gb, 512 SSD). Since updating to 5.2 the Unity Editor has started hanging a lot. Last 3 months on 5.1.x I had probably 5 hangs / crashes. Now 10-30 times per day. It hangs randomly after couple of seconds when returning from MonoDevelop without me touching anything. There's no crash logs generated, just the beach ball forever and I have to force quit Unity.

I have tried every version and patch of 5.2, now on 5.2.3p2. Any ideas anyone? This is worrying. Thanks!

Edit: OSX updated to 10.11.2, Unity 5.2.3p2 continues hanging. It's like a 2 phase thing when returning to Unity from MD, first is does something (auto-compile?) then something more, and it's this second phase where it always hangs. When it's doing its stuff I can't even scroll the console logs, it's responsive briefly between the 1st and 2nd phase. If I click stuff during this (e.g. the play button), it jams even easier. Hopefully this makes sense / is helpful.

 

Has anybody tried 5.3 yet? Are those problems still showing up?