You’re offline. This is a read only version of the page.
Good afternoon!
I have the following problem.
Did the Global compilation, run the CIL Net Framework in and before it runs about 40 minutes. Now it is performed more than 2 hours.
The system is a batch server.
All batch jobs are canceled.
What could be the problem?
*This post is locked for comments
If in brief
TO did Defragmentation cleaned the xpill folder and restarted the procedure. The time was fulfilled
Again, if this is a performance issue then you should be checking the above points and share the details with us, so we could tell you what the next step is for resolving the issue.
What does your CPU/RAM usage looks like on AX AOS / SQL during CIL, what is your hardware spec and layout? Do you have DB locking? Do you see high disk average read/write operations on SQL? Are you doing regular index/statistics maintenance on the AX databases on SQL Server? If you are using physical SQL, do you have dedicated disk storage for that, or it is saturated by other VM's and information stored (if it is a SAN)? And so on.
We do in the test environment.
Last week was 40 minutes.
And which, for example, can processes be launched?
Maybe it's worth removing the daws about the "batch server"?
Changes regarding servers have not been done, the development is actively underway, for this reason we often do these procedures.
SQL physical environment, AOS-Hyper V
Updates are ported by projects, not by models.
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.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (