My Oracle Support Banner

Guide to Optimizing Large Endeca Queries in an Oracle Commerce ATG+Endeca Integrated Application (Doc ID 1952913.1)

Last updated on DECEMBER 06, 2019

Applies to:

Oracle Commerce Platform - Version 9.4 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 and later
Information in this document applies to any platform.

Purpose

Based on experience with customers, we've seen some recurring patterns with applications making one-off queries to Endeca. It can be easy to make a query to Endeca that is slow and/or huge. This can have performance implications.

This document is based on results from performance tuning exercises.

By using some of the rules listed in this document, customers can optimize a lot of Endeca queries (in an ATG + Endeca application) turning a 1, 5 or even 15 megabyte responses into a much smaller 10-100kb responses (thus saving the JVM from excessive memory churn and garbage collection within ATG).

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Details
 Background
 Notes on Endeca Query Response Objects
 Scanning for Standalone Endeca Queries in Code
 Improving Your Queries
 Limiting Which Properties to Return on a Record
 Limit the Number of Records to Return
 Omit Supplemental Objects
 Don't expose all dimensions
 Use Record Filters Instead of Keyword Search
 Use setQueryInfo for Logging Custom Things to Endeca's .reqlog Files
 Don't Ever Set setNavERecsPerAggrERec to 2
 Watch Out for Filtering Based on Timestamps
 Don't Return Key Properties
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.