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?
@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.
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.
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.
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.
