The Reltio platform powers complex implementations. As you plan your implementation, it’s important to predict the impact of your implementation on performance. This article helps you predict performance by providing:

• Baseline latency for the seven API types mentioned in Table 1.
• Factors that affect latency for each API type.

We calculate the latency API types with the following assumptions:

• The tenant doesn't use Lifecycle Actions (LCA)
• The tenant uses the simple address cleanser
• GET requests don't use ordering and scoring
• GET requests don't contain queries to the data history storage
• Transitive matching isn't enabled (the deep parameter is set to 1 in the Get transitive matches )
• POST requests have the URI only parameter set to true

The following table summarizes the baseline (average) latency you can expect:

Table 1. Latency Details

API Call	Description	Baseline Latency, ms
POST Entities API Latency (POST /entities)	Load data into tenant	130
GET Entities API Latency (GET /entities)	Get entities using a filter	47
GET Entity ID API Latency ((GET /entity/{id}))	Find entity by ID	51
GET Entities Matches API Latency (GET /entity/_matches)	Find all matches for an entity	97
GET Entities Tree API Latency (GET /entity/{id}_tree)	Discover tree	260
GET Entities Hops API Latency (GET /entity/{id}_hops)	Get Hops	85
POST Entities Connections API Latency (POST /entities{id}/_connections)	Find Connections	227

We calculated the latency based on the following baseline parameters. Changes in these parameters will change the API latency.

Table 2. Baseline values of Parameters

Parameter	Baseline value (no more than)
Batch size for POST entities	10 entities per batch
Entity size	10 KB
Number of simple attributes per entity	100
Number of nested attributes per entity	10
Number of reference attributes per entity	0
Number of RDM lookups per entity	5
Overall API response size	50 KB
Filter conditions for GET entities	10
Match rules for an entity type	5