AX 2012 excessive compile time

(0) Share

Report

Posted on by Eamonn J. Casey

425

I have just installed AX 2012 on WM Ware, Windows 2008 R2 (incl SQL Server et al). It took almost a day to comple the application. I started the Compile to .NET Framework CIL and kept up'ing the memory as the Ax32Serv.exekept eating it.

After two days it was still running so I stopped it and started again.

Luckily I had a backup so I didn't loose much work. But on my third attempt, there is still the same behaviour.

SQL Server and Ax32Serv.exe seem to be sharing the CPU at about 30%, but Ax32Serv.exe has consumed 600 MB as apposed to SQL Servers 30 MB.

Why has it taken so long?

Is there a memory leak somewhere?

Have I forgetten a magic setting that is not set by default?

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Eamonn J. Casey 425 on at

Like (0)

Report

Additional information:

I have run Performance Monitor and the following values are stable:

Active Sessions: 2

Total Sessions: 12

Server Requests: 41

I start off with a CPU of avg. 18 % that drops to 9 % after AX eats all the memory.

Memory:

SQL     AX

383     215

378     421

549     715

269    1254

48    1584

Only after a few minutes, all my memory is gone and the disk I/O goes up... Increasing the memory to 4 Gb only delays the inevitable.

AX memory stays stable - at MAX.

I have left this run for 2 days and there is still no end in sight!

Was this reply helpful? Yes No
Verified answer

Eamonn J. Casey 425 on at

Like (0)

Report

Seems like that AX does take a LONG time to compile.

Approximatly 3 days on my virtual machine!

So, be patient. There is no memory leak. It's just that AX AOS consumes all of the memory you got to give it! :-)

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

On my laptop running AX locally it takes 1 hr 15 min to run a full compile (level 3) and DB sync. A full CIL build takes 15 min or so.

Runing an i7 processor at 2.5 GHz with 8 gig of RAM and a SSD drive.

Either don't run on a virtual machine or get better hardware. :-)

Was this reply helpful? Yes No
AXT 1,699 on at

Like (0)

Report

Use Windows 7 VHD Boot feature to have the full machine’s power: www.tinusworld.com/.../Run-AX-2012-Hyper-V-image-without-VirtualBox.aspx

Was this reply helpful? Yes No
Volker Breitkopf on at

Like (0)

Report

I can support Alan's information about the runtime(s). And it doesn't make a big difference whether it runs in a virtual machine or not.

Was this reply helpful? Yes No
Dick de Jong 9 on at

Like (0)

Report

seems that it helps to get an SSD disk .. IO is quite a bottle neck ...

Was this reply helpful? Yes No
Dick de Jong 9 on at

Like (0)

Report

@Alan, it is not that we must blame people that they don't have ssd drive, but we should search it in the direction of why do i so desperately need such ...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The excessively long compile times posted above are because of a lack of ram. Your system should have at least 8 GB of RAM. For an in-place upgrade to R2 MS recommends 16 GB. Modern machines should have this.

I believe there is another thread to cover long compile times in R2. Now it takes 4 hours to compile for me.

Was this reply helpful? Yes No
dtdionne 5 on at

Like (0)

Report

Greetings,

Good to hear I'm not alone. First successful (I think) AX install, 2012 R3. I just crossed over the 2.5hr mark on 2 vms, each with 16cores, 128G ram, 2tb vmdk on ssd's

Was this reply helpful? Yes No
dolee 11,279 on at

Like (0)

Report

Starting AX2012 R2 CU7, a new compile tool (axbuild.exe) is available which allows the compilation to be run multi-threaded. It only compiles the application, Full CIL generation still needs to be done using AX client.

See more information here: msdn.microsoft.com/.../dn528954.aspx

Actual compile time varies depends on the hardware. My development VM (SSD, 10GB Ram, i5-2500) compiles AX2012 R2 CU7 in less than an hour (forgot the exact number). AX2012 R3 has a bigger code base but the number shouldn't be drastically different.

Was this reply helpful? Yes No