Sometimes it is faster to do a drilldown, i.e. the filtering is done in multiple steps. For example, the filter expression below filters for a typeId which refers to a custom event type. However, the other filter parameters refer to fields defined in the parent event type. This can make the filtering more expensive.
In such cases it is advised to first replace the typeId by the parent type. Afterwards a drilldown to the for filtering by fields of the custom event type can be done.
For better performance, set enablePageCache to true along with the filter while retrieving the events.
When there are huge number of events satisfying the filter criteria, many subsequent calls are needed for traversing all the pages and retrieving the events. For such cases, we have introduced a new query parameter enablePageCache which can be used as below:
Set enablePageCache to false for first request. For all subsequent request for different pages, set enablePageCache to true.
Set enablePageCache to true for all requests if the new events are getting generated less frequently, i.e. having intervals of more than 10 mins.
When this parameter is set to true, total count of events satisfying the filter criteria will be cached for 10 mins and same cached value will be returned in response resulting in near to accurate value. The event information returned will always be the latest.