Wednesday, March 09, 2016
Find out steps below to resolve Endeca Dgraph Performance issue using Dgraph Flags or minimal configuration.
Thread Count
By Default, Endeca configuration set dgraph thread count as 2. This can be changed to based on Number of core – 3 in DgraphDefaults.xml
<arg>--threads</arg>
<arg>2</arg>
–whymatch debug flag
Endeca App default sets --whymatch flag as true.
This flag is used for debugging, why a particular record is being returned and why it matched. This flag is not recommended for production environment.
--cmem flag
The Dgraph cache is used to dynamically cache query results.
The default Dgraph cache size (specified by the --cmem flag) is 1024MB (1GB).
This flag needs to be tuned at least double the index size to get better performance.
Optimal use of dgraph group while setting up dgraph live cluster
restartGroup property under dgraph node in LiveDgraphCluster.xml is used to push indexes to all dgraphs that fall under the same group. Value can be defined as A or B or any character. Make sure to create two groups of 50% each both for baseline and partial.
updateGroup is used for partial updates.
Click here to view Endeca Query Performance issues and Fixes.
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
Click here to view Endeca Query Performance issues and Fixes.
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
1 comment
I can’t imagine focusing long enough to research; much less write this kind of article. You’ve outdone yourself with this material. This is great content. Abschleppdienst Hamburg
Post a Comment
Note: Only a member of this blog may post a comment.