Boosting performance by trimming the response JSON

While adding an extra result field to a query or an extra response node to an Integration Procedure JSON may seem insignificant, let’s see how this may affect performance. Let’s see whether we should pay attention to this small thing or not. Let’s start with DataRaptors and see the exact performance impact that reducing the number of response fields may have.

DataRaptors

Let’s compare two DataRaptors that extract the same data from the same object but return a different number of fields. Here’s a sample OmniScript with two DataRaptor Extract Action elements:

Figure 9.20 – An overview of our test OmniScript with two DataRaptors

Both DataRaptors retrieve a single record from the Test_Obj__c object, but the first one retrieves and returns more fields than the second. Both DataRaptors have the same filter criteria and extract the same amount of data but use different...