Developer forum

Currently discussing: Plans to implement a Consent module for GDPR compliance.

Join the discussion!

Forum » Integration » Ax2012 Integration slow response times

Ax2012 Integration slow response times

Arnór Halldórsson
Arnór Halldórsson
Reply

Hi everyone,

Is there anybody out there who has integrated against AX2012 and could tell me if there are any configs that can be made on the AX webservice provided by DW to optimize speeds.

We've been running stress tests directly on the webservice from LoadUI (bypassing the Dynamicweb Connector Service), and the results are that the response times get very slow for only a few simulated users sending rather small requests. We have a LoadUI setup with 10-50 virtual users sending a batch of:

  • 1x GetEcomData request containing 17 products
  • 17x GetEcomData requests containing only 1 product per request
  • 2x CalculateOrder requests

over a period of 5 minutes. The response times for the big GetEcomData request and the CalculateOrder requests are the most problematic where the average response times are over 15k ms when we simulate 20-50 users using the system at a time.

We've eliminated SQL query-ing in AX as the culprit, that part runs smoothly and quickly, but something in the webservice is causing this slowness. Are there any configs that could be configged to optimize this or are we faced with upping the hardware and/or refactoring the code?

Best regards,
Arnór

Replies

 
Nicolai Pedersen
Nicolai Pedersen
Reply

Hi Arnor

I've asked a developer to look into this and see if we have something in the code that could be the cause of this. Will get back.

BR Nicolai

 
Dmitriy Benyuk
Reply

Hi Arnór,
are you using the encryption/decryption on your requests from Dynamicweb Connector to AX?
Its present in the sevice config file:
<appSettings>
<add key="Secret" value="test"/>
If yes, could you check if removing it:
<add key="Secret" value=""/>
helps to improve the response time?
Regards, Dmitrij

 
Arnór Halldórsson
Arnór Halldórsson
Reply

Hi Dimitriy,

Thanks for the quick response.

In the tests I mentioned above we are bypassing the connector service and sending requests straight to the AX webservice :)

We are however using the secret key in the connector service that the web talks to, I'll try removing it and see if the web get´s a speed bump, but currently it seems that AX is the main bottleneck.

Best regards,
Arnór

 
Dmitriy Benyuk
Reply

Hi Arnór,

Which version of the AX code units do you use? V1(DynamicwebIntegrationFrameworkAxExampleCode.zip) or V2(Integration v2 - AX2012 (2.0.0.BETA).zip) code units?
What is your current hardware setup (CPU cores, Available RAM, Available disk space)? If SQL Server is running on the same machine then you should make sure that it doesn’t take up all resources. See Microsoft Dynamics AX 2012 System Requirements.
What is the AX version and build number? Example: AX2012 R3 CU13 (6.3.6000.149)

There are some tools available for monitoring AX performance that might be useful:
https://community.dynamics.com/ax/b/axresources/archive/2014/09/09/performance-resources-for-microsoft-dynamics-ax
Regards, Dmitrij

 
Arnór Halldórsson
Arnór Halldórsson
Reply

Hi,

  1. We're using AX code unit V1.
  2. Currently we're running on 4 CPU cores, 16GB RAM, not sure about the disk space though.
  3. The SQL server is hosted on another machine, and we've elminated the SQL as the bottleneck.
  4. AX version is CU13.
  5. We have been using these tools :)

We have discussed upping the hardware drastically, and we probably will before going fully live. That should ease the pressure somewhat when multiple users are using the system but we're afraid that we'd still be faced with overall slow response times.

Br, Arnór

 

 

You must be logged in to post in the forum