Reltio Connect

Do you have to create a support ticket to make this happen? #dataextraction​​

------------------------------
Siva Krishna Akuthota
Advance Auto Parts
------------------------------

The payload size itself is based on your data model and the attributes that you have persisted inside of Reltio. If you have a data model that only has four attributes, first name, last name, phone number, and email, and you only have one value per attribute, it will be small.  If you have a data model that has 1000 attributes, and you have seven instances of each attribute, it will be big. It is not only dependent on your data model, but it dependent on the data inside of that object.

By default, in the Reltio Events API, a message publishes no attributes. That definition is defined in your tenant configuration. Today, our support team or your customer success manager can help you with that process to apply that change to your tenant config. Or for our customers that are our concierge support customers, your technical account manager can go ahead and make that config change for you directly without the need to go through the support team.

For a deep dive on Reltio Data Extraction, watch this webinar

------------------------------
Mike Frasca
------------------------------

Along the lines of what Mike has said, the number of attributes in a payload is within control and it depends on the data model and the populated data. Reltio recommends configuration best practices for optimum platform performance. One of those practices states that the "Max number of populated attributes in an entity: 200" (https://docs.reltio.com/infoandconfig/bestpractices.html).

Theoretically, the maximum attribute value can be increased beyond 200. However, the physics of payload size versus network transmission has an impact on performance.

From our simulated experiment, we found that the threshold of 200 populated attributes is a practical way of limiting API request payload byte size to avoid long latency, timeouts, and network issues. It boils down to the physics of payload size versus network transmission. Regardless of whether a count of populated attributes is made at the entity or attribute level, it is simply a count of 200 key-value pairs which approximates tens of kilobytes payload size. Therefore, Reltio platform performs optimally when request payload size is kept below tens of kilobytes, and this is easily approximated by keeping the count of populated attributes less than 200.

------------------------------
Olu Ojo
Intel
------------------------------

Original Message:
Sent: 07-01-2021 17:31
From: Siva Krishna Akuthota
Subject: How do we control the number of attributes sent in the payload?

Do you have to create a support ticket to make this happen? #dataextraction​​

------------------------------
Siva Krishna Akuthota
Advance Auto Parts
------------------------------