Factors for GET Entity ID API Latency

Scenario: Retrieve an entity directly from the primary data storage using unique entity identifier (GET /entity/{id})

Baseline latency: 51 milliseconds

Table 1. API Latency Details
Factor Baseline parameter value One step increase from baseline Average latency increase by 1 factor step, % from baseline Average latency increase by 1 factor step in milliseconds Max analyzed value
Response size 50 KB each additional 50 KB 19.6% 10 200 KB
Crosswalks per entity 10 every 10 additional crosswalks 39% 20 50
Simple attributes per entity 100 every 100 additional attributes 58.8% 30 500
Nested attributes per entity 10 every 10 additional nested attributes 196% 100 30
Reference attributes per entity 0 each additional reference attribute 196% 100 5
RDM lookups per entity 5 every five additional lookups 294% 150 25
Another factor to consider is that defining a specific time frame to extract the entity as it was within that time frame:
  • triggers data extraction from the history data storage and
  • adds up 600 ms to the latency on average