Last updated on DECEMBER 20, 2016
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.1.0 and later
Information in this document applies to any platform.
Encountering a performance issue where the dgraph request log showed some large response sizes being returned.
In the above example, the response size was 34,246,153 bytes (which equals just over 34 MB), the request round-trip time was 608,344.56 ms and out of those time dgraph engine-only time was 16,584.08 ms.
In this case the response is returning up to 16000 records which is contributing to the large response size (indicated by the nbins=16000 value), but in other situations perhaps large query response size is happening because too many supplemental objects are returned (these objects are related to Rule Manager or Experience Manager rules/content items being triggered), or you have a very large, flat dimension structure and with the use of allgroups=1 (automatically expanding all refinements) it is returning many dimension values.
This article explains how to capture objects that are included in a query response so it will help to investigate a performance issue further.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms