Views:

Applies to Product - Power Apps

What’s happening?
Customers have reported concerns regarding API limitations and throttling while conducting performance testing for applications, particularly when simulating a high number of concurrent users.
 

Reason:
The performance testing method involved using a limited number of test accounts to simulate a larger number of concurrent users, which may lead to throttling due to user license limits. Additionally, the primary performance constraint identified is the API call limits per connection.
 

Resolution:

  1. Understand the testing setup and its implications
    • The testing team used 50 test accounts to simulate 250 concurrent users by looping through the same accounts multiple times.
    • This approach may have contributed to the observed performance issues due to exceeding per-user or per-connection API limits.
  2. Evaluate performance symptoms
    • The average response time for login events varied significantly, with some logins taking up to 11 seconds.
    • This raised concerns about the application's performance under load.
  3. Review API throttling limits
    • The Dataverse connector documentation specifies a limit of 6,000 API calls per 300 seconds per connection.
    • These limits should be factored into performance test planning to avoid triggering throttling.
  4. Recommendations for performance testing
    • Involve the performance testing team in discussions to clarify their methodology.
    • Ensure the number of test accounts used aligns with the number of simulated users to avoid artificial throttling.
    • Consider distributing load across more accounts or connections to stay within API limits.
  5. Further troubleshooting
    • Review internal telemetry and Kusto queries for any backend errors or anomalies.
    • If needed, escalate to the appropriate support team for deeper investigation.
Public Documentation on API Throttling