Factors for GET Entities API Latency
Scenario: Find and extract a set of entities based on the filtering condition (GET /entities)
Baseline latency: 47 milliseconds
| 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 |
|---|---|---|---|---|---|
| Conditions in filter expressions | 10 | every 10 additional conditions | 1% | 0.5 | 40 |
| Average size of the entity in result | 10 KB | every 10 additional KB | 2% | 1 | 50 KB |
| Nested attributes per entity | 10 | every 10 additional attributes | 12% | 6 | 20 |
| Simple attributes per entity | 100 | every 100 additional attributes | 27.6% | 13 | 300 |
| Count of results in response | 5 | every five additional results | 38.3% | 18 | 25 |
| Crosswalks per entity | 10 | every five additional crosswalks | 38.3% | 18 | 15 |
| RDM lookups per entity | 5 | every five additional lookups | 42.5% | 20 | 25 |
| Reference attributes per entity | 0 | each additional attribute | 85% | 40 | 5 |
Two other factors to consider for GET /entities API latency include:
- If you enable the score flag in the API query, you add up to 115 ms to the latency on average.
- If you enable ordering in the API request, you add up to 9 ms to the latency on average.