Personalization services can impact template rendering and search request performance.
Though Predictive Sort can affect your page performance, it doesn't affect
search-show pipeline performance. However, using Predictive Sort
does come with caching considerations when rendering templates and performing search
requests. Make sure to follow best practices for improving site performance when using
Predictive Sort.
Rendering Templates
Because every shopper sees a personalized sort of their search result set (search hits), caching the position of the search-hits on the product grid isn't possible. B2C Commerce automatically overrides the related caching tag defined in the rendering template. There is no need to modify the caching setup in the rendering temples.
The caching of search hit positions in the grid is disabled by default only if requests include a sorting rule that includes the Predictive Sort sorting attribute. This means that non-personalized sorting still uses the default caching configuration.
For example, if you assign the Predictive Sorting Rule as the default sorting rule to only the Sales Category, only caching for the Sales Category Product Listing Page is disabled. If you configure an A/B test with 5% traffic to the Predictive Sorting Rule, caching is only disabled for these 5% of requests.
Search Requests
To use Predictive Sort, verify your ISML templates use the iscache if attribute. By changing the template, search requests using a sorting rule with Predictive Sort are no longer cached.