RE: Long CIL Net Framework Ax12 RTM
If you are talking about a Production instance, then I would say your processes are wrong.
Doing customizations and building CIL in a Production environment is not recommended at all, it is supposed to be compiled in your Build/Staging environment. Once completed, you will shut down your AX AOS instances, and release the AX ModelStore containing the source code, p-code and compiled CIL to Production.
Have a read about promoting changes between environments in the official whitepaper:
https://technet.microsoft.com/en-us/library/hh292604.aspx
If you absolutely must do a CIL compilation in Production, you should only do it while a single instance is running without any users connected to the system, and no other processes running (like a batch job).
If performance is bad for the compilation, then it is an indication for:
- not having enough resources on your AX AOS (CPU/RAM)
- not having an index / statistics maintenance for your SQL Server
- other performance issues related to SQL (incorrectly configured trace flags, wrongly designed disk layout for data/log files and TempDB, latency problems, DB locking, etc.)
An 8-core environment, with 16 GB RAM and a locally hosted database sitting on SSD disks on a Build instance can do Full CIL in 10-20 minutes tops. You should be doing it on a dedicated server as well.