Tuesday, April 05, 2016
Endeca maintains internal Dgraph cache at Dgraph level. Endeca Dgraph cache gets flushed during baseline and partial update process.
Behaviour
Most of the client utilize Endeca partial update, for inventory update , product updates etc., in every 30 minutes or so. There could be a possibility to have slow Endeca query response time and delay to process the request.
Solution
Dgraph performance can be improved by warming the internal Dgraph cache after an update has been processed.
Specify the --warmupseconds <seconds> flag to the Dgraph to warp the Dgraph Cache. The --warmupseconds flag instructs the Dgraph to store a client sample queries, and after an update is
processed, the Dgraph internally re-runs a sample of those queries to warm the cache.
All warming query URLs are tagged with the additional parameter &log=warming in Dgraph request logs.
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
Behaviour
Most of the client utilize Endeca partial update, for inventory update , product updates etc., in every 30 minutes or so. There could be a possibility to have slow Endeca query response time and delay to process the request.
Solution
Dgraph performance can be improved by warming the internal Dgraph cache after an update has been processed.
Specify the --warmupseconds <seconds> flag to the Dgraph to warp the Dgraph Cache. The --warmupseconds flag instructs the Dgraph to store a client sample queries, and after an update is
processed, the Dgraph internally re-runs a sample of those queries to warm the cache.
All warming query URLs are tagged with the additional parameter &log=warming in Dgraph request logs.
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
4 comments
Hi Ajay,
We are getting below error in application log. configured F5 switch for LoadBalancing.
we configured the Endeca restart group between as 2 MDEX in Agroup and 2 MDEX in Bgroup.
while indexing MDEX will restart at the time LB is passing the request to the restarting MDEX.?? so, we are getting below error or any other config reason as line time interval settings in LB?? kindly help me...
Thanks
**** Error /atg/commerce/endeca/cache/DimensionValueCacheTools An error occured while attempting to determine the MDEX data_date and num_generations java.net.SocketException: Connection reset
**** Error /atg/commerce/endeca/cache/DimensionValueCacheTools Could not retrieve the data_date from the MDEX
**** Error /atg/commerce/endeca/cache/DimensionValueCacheTools Could not retrieve the num_generations from the MDEX
Thanks
sry forget mention above..Application log means ATG server log
Thanks for your personal marvelous posting! I definitely enjoyed reading it, you can be a great author. I will make sure to bookmark your blog and will come back from now on. I want to encourage you to definitely continue your great job, have a nice evening! all of craigslist
Thanks Werner for referring my blog.
Post a Comment
Note: Only a member of this blog may post a comment.