Tuning tips for snippeting

Enabling snippeting affects query runtime performance.

You can minimize the performance impact on query runtime by limiting the number of words in an attribute that the Oracle Endeca Server evaluates to identify the snippet. This approach is especially useful in cases where a snippet-enabled attribute stores large amounts of text.

Provide the --snip_cutoff flag to the Dgraph to restrict the number of words that the Oracle Endeca Server evaluates in an attribute. For example, --snip_cutoff 300 evaluates the first 300 words of the attribute to identify the snippet.

If the --snip_cutoff Dgraph flag is not specified, or is specified without a value, the snippeting feature defaults to a cutoff value of 500 words.

If a snippet is too short, and you are not seeing enough context words in it, increase the value for SNIPPET_SIZE in the configuration document. See the topic for enabling snippeting for the detailed format of the configuration.