Factors for GET Entities Hops API Latency
Scenario: Retrieve the hops of an entity directly from the primary data storage using unique entity identifier (GET /entity/{id}_hops)
Baseline latency: 85 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 |
|---|---|---|---|---|---|
| resultsCount | 1 | every additional five results | 100% | 85 | 50 |
| Depth | 1 | each additional level of depth | 90% | 76.5 | 20 |
| Hops | 1 | each additional hop | 30% | 25.5 | 20 |
| RDM Lookups | 60 | every five additional lookups | 10% | 8.5 | 200 |
| RDM Transcodes | 2 | every two additional transcodes | 50% | 42.5 | 20 |
| Crossworks count | 10 | every 10 additional crosswalks | 50% | 42.5 | 100 |
| Simple attributes | 100 | 3 ms (every 100 additional attributes) | 10% | 8.5 | 500 |
| Nested attributes | 10 | every five additional attributes | 10% | 8.5 | 50 |
| Reference attributes | 1 | each additional attribute | 30% | 25.5 | 5 |
| Response size | 2 Kb | each additional Kb | 30% | 25.5 | 100 kb |