Make your reprocess actions as specific as possible
Reprocess actions can cause execessive processing, especially if you reprocess more than needed. This could result in a larger queue of jobs, and it will take longer for all your views to be updated. Because of that, it’s important to make your reprocess actions as precise as possible, by usingoriginId or a precise filter so you only target the schemas and source entities you actually need to reprocess.
Read more about reprocessing.
Exclude properties from lookup if you don’t need them
By default when you do a lookup in a schema, the entire source entities are loaded from storage, including theproperties object.
Full source entity including all custom properties
originId, originParentId, or url.
In these cases it’s important to specify that in the lookup, as this will improve performance and lower the amount of time it takes to generate views.
You do that by setting excludeProperties to true in the lookupOptions parameter.
lookup with excluded custom properties