Facet Configuration: Best Practices
- Lance Bohrnell (Unlicensed)
Table of Contents
Overview
Field and facet configuration impacts index size and payload size, which has an impact on indexing time and engine performance. The following guidelines are standard best practices, your configurations may vary depending on your data, business requirements and use cases.
The number of facets and the number of facet values has a direct relationship with the response time of your engine. This is due to a number of factors such as
Serializing the payload
Cardinality between all the facet values is a heavy operation
Facet Best Practices
Limit number of values within a facet to under 200
Define Coverage
Utilize Facet Overrides on Landing Pages
NOTE: In some unique instances, when there are an extreme number of facets configured in the workbench this can increase the response times. If Hawksearch sees this as an issue, we will call this out during your implementation phase.
Other Options for Reducing Payload Size
Payload size is directly related to the Field and Facet Optimization previously discussed.
Other options for reducing payload size include:
Limiting the number of products on the page
Utilize pagination or lazy loading
Types of Analyzers
This section outlines the available analyzers. There are five analyzer options that are available for the business user to select. The selection of an analyzer will override the default indexing configuration “Hawk Search Analyzer”. Each analyzer is explained below.