Compiling time question

Hello guys ,

I want to ask a question as designer. When ever I change a line code save and return to unity I'm waiting 30-40 sec. My project size is like 10 gb. alot of models and textures 1844 scripts with all plugins. I locate my scripts in Standart asset folder. Plugins are in Plugins folder. I use assambly files for in script folder under all categories. My auto refresh is turn off , Because asset update is really pain for me When ever When I go another windows app , then return back , Unity check all assets. It is long time for me, I hate Auto refresh and close it but know Whenever change code, I am waiting for 30-40 sec. I update manually. Is this normal proccess or any idea or tips How can I reduce this time. I try assembly files but nothing happen. Please help me

 

Where are 'above 100' options? Or are the listed values already in hours?

 

I'm not sure compile time is related to the size of the project.

It must take about one or two seconds for me.

 

I generally see no more than a few seconds no matter the project.

 

@Brathnann @AnneSchmidt Thanks for answer. How can I detect which part of code compile take too much time ? Do you have any idea ? Profiler can find compile time ?

 

Maybe it's not the compiler but your computer?

 

@AnneSchmidt I have Core i7 4770k cpu , I dont think is depending on computer.

 

If you update/reimport a Script file, Unity performs an assembly domain reload and triggers all sorts of initialization and callbacks.

I saw the following callbacks often to be a reason for slow reloads/compiling:

• https://docs.unity3d.com/Manual/RunningEditorCodeOnLaunch.html
• https://docs.unity3d.com/ScriptReference/InitializeOnLoadAttribute.html
• https://docs.unity3d.com/ScriptReference/InitializeOnLoadMethodAttribute.html

 

If depends on how busy your computer is when you have a new script to compile.

 

CPU speed always matters. For large projects with lots of source files disk speed matters too. In Unity there are additional things to compile, like shaders, and a lot of things which may have recompression trigger, like textures and sound. Doing so in parallel saves time, but doing things with large files in parallel costs disk performance, so a good SSD is key. The more cores you have, the more you need that SSD.

There's another thing which can slow down compilation immensely: Log output. Printing lots of warnings could actually double compilation time if they're scattered all over your code. Everything stops when printing, and doing it thousands of times has a significant impact. In other words: Write clean code and fix every warning. Microsoft have mentioned this in their Visual Studio documentation, and it holds true for Unity too.

 

@orb Thanks for your answer. My project is already in ssd disk but you said like I have 290 warning and I ignored all the time I will fix them. I hope it will be fix the speed. Thanks If I gain a speed , I will write here

 

Never seen extreme compilation times, and we're having a big code base at work. Though the code base is seperated into assembly files and we're only working directly in the project's code on new features. It doesn't take long to make any changes, 1 or 2 seconds until Unity starts and another 2 or 3 seconds to complete.

Perhaps it is caused by lots of instances of the scripts, that have to be adjusted. I mean, for all the types that have been changed, the serialization layout could have changed and thus all instances have to be serialized again, in order to support the changes.

Just for testing purposes, it might be worth creating a new project. Throw all the assets and scripts from your original project in, and make a change in the scripts. If that runs significantly faster, the scene updates + all instances may cause the extreme times you're facing.

 

I try to delete folders then realize , There are a lot of empty folders in my project , I clean them and now it is better performance, I think when I change something , Editor search all folders. This take some times. It is better now but It still is not perfect. I will update more here If I find usefull information , for next generations.

 

When I change a script file and head back to the editor it normally takes between 5 and 15 seconds depending on which computer I'm on. In my project if I switch between platforms (windows to linux, or x86 to x86_64) I'm looking at 10+ minutes, 20+ on my laptop. If I delete my library folder I'm looking at 25 minutes on my desktop and an hour on my laptop.

 

I'm facing the same issue. Same project size, same computer. But switched from Windows 10 to Ubuntu 2019.10. Compilation takes more time. About 20 seconds. On Windows, it was 1 or 2 seconds.

 

@Achie1 Hello ,I solved asset update problem. It is very weird. I formatted to windows and asset updates will ok now but
My compile time are 60 seconds now, after a year, I am very happy with that. I am not programmer , I am artist and I was learning programming. I read alot of articles about assemblies. I will write spaghetti code (Somestimes unity crash while compile) and all assemblies reference each other. and my project is very big now. I dont know how to solve it but If I will have time for it I should repair all scripts and references. God bless me

 

The same project, the same computer, On Windows 10, compilation time : 1 or 2 seconds. On Ubuntu 2019.10, compilation time : 6 or 8 seconds