David Staudt | Beyond the built-in throttling, there aren't any firm guidelines for AXL/RIS transaction rates, beyond the admonishment to have some understanding of the impact of the requests, test carefully, and self-throttle if warranted.
A place to start would be to observe the overall OS health (CPU, RAM, disk I/O) to see if there is anything growing out of control, then focus on standard IIS health indicators that would be relevant to the AXL web service. A typical problem scenario involves apps submitting requests faster than AXL can respond, resulting in a backlog which eventually consumes resources.
If the server is not burdened and nothing obvious is happening in the performance counters, I would recommend opening a formal case with Developer Services so we can investigate in depth. Making sure the latest version/SR available is installed is always a good idea. |