Friday, March 25, 2016
The Endeca Assembler and Experience Manager work together to provide the dynamic experience.
Experience Manager - Provides an interface to manage content configuration, enabling content administrators to create a targeted and compelling customer experience.
The Endeca Assembler - Provides a unified interface for all content queries. The Assembler extracts information from the request and makes a query to the MDEX Engine to retrieve the configuration(Rule, Thesaurus, Stemming etc).
Query Processing Flow - Application sends the request to the Endeca Assembler once the request comes from the user and Assembler fire a content query to MDEX to get the configuration to display a page. Point 2 and 3 are still valid for 11.2 version as thesaurus, stemming etc data is required for rule expansion.
Here is the comparison cart below over multiple versions of Oracle Endeca releases. This Comparison talks about Endeca Content query response as per query process flow, daigram above, point 2 and 3.
As per my analysis above, 11.2 version gives very good performance benifit in terms of Assember content query response time, size and remove application server dependency from IFCR repository.
Click here to view Dgraph Performance Tuning
From Author
Was this post resolve the Endeca Performance issue? what do you think, making above steps may resolve most of the issues? Provide your comments
No comments
Post a Comment
Note: Only a member of this blog may post a comment.