My Oracle Support Banner

F.A.Q. About Internal MDEX Behavior Related to Memory, I/O, and Performance (Doc ID 1575438.1)

Last updated on JANUARY 20, 2020

Applies to:

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

Purpose

This article is a summary of general observations made by Oracle Commerce Support related to the performance of the MDEX.
The answers in this article should by no means be considered absolute, as they are subject to change or become outdated as new product releases become available.
Information may be added or improved over time as new questions arise and discoveries are made.

Questions and Answers

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
Questions and Answers
 What are the observed MDEX I/O characteristics, and how do they affect the performance of Endeca applications?
 Does Oracle recommend flash-based solid state drives (SSD) for disk storage for MDEX usage? If so, what are the characteristics to expect?
 How does cache warming behave regarding MDEX thread usage?
 What are the best areas to focus on for improving performance for my app in particular?
 How does the MDEX utilize all the index data it has on disk at start up?
 Why would a Partial Update trigger a longer period of swapping and higher disk IO in the MDEX than when an MDEX is started at the end of a Baseline Update?

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