Factors for GET Entity Matches API Latency
Scenario: Find all the matches for an entity (GET /entity/_matches)
Baseline latency: 97 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 |
---|---|---|---|---|---|
Response size per entity | 10 KB | every 10 additional KB | 5% | 5 | 50 KB |
Nested attributes per entity | 10 | every 10 additional attributes | 5% | 5 | 30 |
RDM lookups per entity | 5 | every five additional lookups | 5% | 5 | 60 |
Results count | 5 | every five additional matches in the result | 20% | 20 | 20 |
Crosswalks count per entity | 10 | every 10 additional crosswalks per entity | 20% | 20 | 15 |
Simple attributes per entity | 100 | every 100 additional attributes | 20% | 20 | 300 |
Match rules for an entity type | 5 | every five additional match rules | 31% | 30 | 20 |
Reference attributes per entity | 0 | each additional attribute | 72% | 70 | 5 |