Android il2cpp build is too slow compared to iOS

My build machine will complete the ios il2cpp build in 20 minutes, android mono build in less than 10minutes.
But, Android il2cpp build has over 7 hours. (ARMv7, ARM64, 3.5 hours each)
Can you think of anything that might have caused it?

https://docs.unity3d.com/Manual/IL2CPP-OptimizingBuildTimes.html
This has already been tried.

```
Invoking il2cpp with arguments: --convert-to-cpp --emit-null-checks --enable-array-bounds-check --dotnetprofile="unityaot" --compile-cpp --libil2cpp-static --platform="Android" --architecture="ARMv7" --configuration="Release" --outputpath="/Users/username/.jenkins/jobs/project_name/jobs/project_name.task.android.test/workspace/client/Temp/StagingArea/assets/bin/Data/Native/armeabi-v7a/libil2cpp.so" --cachedirectory="/Users/username/.jenkins/jobs/project_name/jobs/project_name.task.android.test/workspace/client/Assets/../Library/il2cpp_android_armeabi-v7a/il2cpp_cache" --additional-include-directories="/Applications/Unity/Hub/Editor/2018.4.5f1/PlaybackEngines/AndroidPlayer/Tools/bdwgc/include" --additional-include-directories="/Applications/Unity/Hub/Editor/2018.4.5f1/PlaybackEngines/AndroidPlayer/Tools/libil2cpp/include" --tool-chain-path="/Applications/android-ndk-r16b" --map-file-parser="/Applications/Unity/Hub/Editor/2018.4.5f1/Unity.app/Contents/Tools/MapFileParser/MapFileParser" --profiler-report --directory="/Users/username/.jenkins/jobs/project_name/jobs/project_name.task.android.test/workspace/client/Temp/StagingArea/assets/bin/Data/Managed" --generatedcppdir="/Users/username/.jenkins/jobs/project_name/jobs/project_name.task.android.test/workspace/client/Temp/StagingArea/Il2Cpp/il2cppOutput"
```

I upload the profile by "--profiler-report".
(renamed profile.txt from profile.json)

Environment:
- Unity2018.4.5f1
- .NET 4.x

Build Machine:
- Mac Pro (Late 2013)
- macOS Mojave 10.14.6
- 3.5GHz 6-Core Intel Xeon E5, 64GB Memory, SSD

 

Thanks for your reply!
I try to collect the files, ios and android each.
I want to send by private message, because the project is production.

I send there files to you by conversation.
Please check it.

 

Was there any resolution for this? I am on 2021.2.7 and Android is taking sooooo much longer than other build targets and compared to 2021.1.28 it also is much slower. Is there any way to debug the culprit of this? It is for example stuck at libil2cpp.so for many minutes without any progress until it finally hands it over to gradle.

 

I can confirm it's incredebly slow. I tried to build one scene Low-poly it takes me 28 minutes with il2cpp enabled

I tried many versions of Unity all the same results with the newer version it's even worse

 

I will try to look on 2022 but unfortunately many google services won't work with 2022.

The problem is that I have another game in il2cpp but much heavier and we are talking about almost 700MB but build only takes 2 minutes instead with a Low-poly scene only 10k vertices takes 28 minutes.

Update Edit:
yes currently on 2022 it works well. My project and the scenes look wonderful.
Well I'll try for now 2022.
How beautiful 2022 looks like.

Build Time first was 28 min... ver (all)2021
now 37 seconds with 2022 version

 

I was shocked too. The only thing I noticed is that the event system no longer works on android Unity 2022. I always used OnMouseDown to check for collider for example
if (EventSystem.current.IsPointerOverGameObject())
return;
is there another method around because i did not find anything actually Pointerdown not work for me either

 

Okay i come back to old version of unity 2020 because 2022 is unstable... now the build is not anymore 28 minutes but 2 hours

 

Sorry for digging this one up, but there's anything specific here that you would like to take a look @JoshPeterson, most because I'm dealing with a similar issue. Our project its a live project with almost 7 years of live service, so this has been upgraded between multiple unity versions and we are in 2019 (on the brink of going 2020) but our il2cpp build times takes a really long time, I'm wondering what you would suggest to understand why

 

Having this issue on Unity 2022.3.0 . While on iOS the build time on I2LCPP is 3 minutes aprox... for android takes 30-40 minutes.... there's something really wrong here.
Can't say how much took to build for android in prior versions since this is the first time.

 

I have it on Release. I even changed the IL2CPP code generation to Faster (smaller) builds to no avail.
Anything else i should check ?
Thanks for your help

 

Also one of the things that caught my attention is the amount of time the window 'Cloud Diagnostics Symbol Upload' shows up..... probably stays there for 10 min or more... although maybe is not what its internally doing... I thought i should share it.

 

Where could I see this children?

I've realized everytime I make a build, no matter if it's just 1 line of code the 'build and run' or the 'patch and run' do a new build... at least 15 min... on another thread they told me its possible some script is changing dependencies in the Build.IPreprocessBuildWithReport.OnPreprocessBuild call. Do you think this can be the case?

Thanks a lot for your help!

 

Im on MacOS Sillicon Ventura 13.1

 

Does this tell something?

 

I uninstalled Unity Diagnostics long ago, I've been looking around the project to see if theres still something left but I dont find anything... any idea where this might come from?

Child view at a later point of the build:



and another one:

 

Ill try

 

I got rid of it!!! by installing the package again, disabling, and uninstalling. Now it doesnt appear anymore, incremental builds are faster, not as fast as someone told me should be (10-20 seconds) but now takes maybe 6 minutes aproximately, is this timing inside of what we can consider normal? (This is an incremental build with script debugging on)....

Curiously, now the step that takes the most time is 'Incrementally deploying to ..." At the beggining i thought maybe it was transferring the build to the device via wifi but now is everything connected by usb and still taking quite some time.

Thanks again for all your help.

 

Even for an incremental build?

Just testing and no, not 6 minutes, Incremental building takes already :
>10 -15 minutes at least 'Building Gradle Project' (does an incremental build need to do so?)

 

20-25 minute builds have been normal with Unity for a while now (at least with IL2CPP and Master config)

The same project on the same machine takes around 3 minutes on iOS (and another 2-3 for archiving on XCODE if we want to make things equivalent)

I don't really think Unity is at fault though, really. When we used to export to a gradle project, exporting from Unity was fairly quick (under 10 minutes maybe closer to 5?), and then android studio took forever.

I'm just posting here so that you know that from our experience going from Unity to an actual device, takes 5 to 10 times longer on Android than on iOS.