IntelliTrack

Appearance

VeriMy Load Test Report – Technical Summary ​

January 31, 2025

A summary of how the APIs behind VeriMy performed under load, and the recommended limits for enabling and registering VeriMy devices in bulk.

Overview ​

The VeriMy Load Test Report details performance evaluations of API functionalities supporting the VeriMy system. The tests examined API operations under varying loads, service tiers, and durations, with results providing insights into system scalability, stability, and resource utilization.

The testing was conducted using Apache JMeter and executed on Azure Load Testing, a managed cloud-based service for high-scale API performance testing. The key VeriMy-related operations tested include:

  • VeriMy Enable – API function enabling VeriMy on an IntelliTrack asset.
  • VeriMy Disable – API function disabling VeriMy for an asset.
  • VeriMy Register – Registration process for new VeriMy-enabled assets.
  • VeriMy Checkout – Asset usage check-out process.
  • VeriMy Check-in – Asset usage check-in process.

Key Assumptions and Considerations ​

  • Tests were performed in the Staging environment with similar configurations to Production.
  • Production uses shared API endpoints, meaning high tenant loads may impact overall system performance.
  • Each tenant has a dedicated database, while the root database manages system-wide functions, including authentication and authorization.
  • The root database baseline load in production ranges between 12% and 25%, and test environments were adjusted to reflect similar conditions.

Summary of Findings ​

VeriMy Enable ​

  • Adds ~10% CPU load to the root database across tested service tiers.
  • Performance declines as the number of devices enabled increases.
  • No database connection failures or deadlocks were observed.
  • Recommendation: Cap simultaneous bulk Enable to 5,000 to maintain performance.

VeriMy Disable ​

  • System handled high disable loads efficiently without performance degradation.
  • CPU usage for the root database stayed below 7%, and the tenant database peaked at 9%.
  • No significant system strain was detected.

VeriMy Register (deploy and launch VeriMy on the device) ​

  • Resource-intensive operation, with failures occurring at high loads.
  • At 3,000 registrations, root database CPU usage hit 100%, leading to significant slowdowns.
  • Recommendation: Cap simultaneous registrations to 1,000 per 20 minutes to maintain performance.

Checkout & Check-in ​

  • Consolidated endpoint for checkout/check-in improved performance.
  • Removing redundant API calls reduced network overhead.

Authentication Token Generation ​

  • Token creation endpoint is a critical performance bottleneck.
  • Extended token expiration time to reduce performance bottleneck.

Additional Recommendations ​

  1. Monitor Deployment and Usage:
    • Track CPU/memory utilization, database load, and system errors during large enterprise deployments > 3,000 devices.
    • Adjust service tiers dynamically based on observed demand.

This summary captures the high-level findings and recommended actions from the VeriMy Load Testing Report, focusing on system scalability, API efficiency, and authentication optimization.