This content has been marked as final. Show 3 replies
Hi Sunil1 person found this helpful
Are you definitely not using MDEX 6.1.3 (you entered this originally then edited it)? I could see this happening on 6.1.3 if you have wildcard search enabled - there is a bug in that version that causes a memory leak (when a customer makes a wildcard-only search that gets past any web application checks for minimum characters, e.g. ***). No idea what could cause this in 6.2.1. Is this the same issue as you previously reported, and did you follow any of the steps outlined by the respondents on that thread?
Hi Sunil,1 person found this helpful
did you try running perf tools to see what results you were getting ?
running a reqloganalyzer (if you are running MDEX 6.2 the new name of Cheetah) with a --showAll flag, share the results and see if there is anything unusual in the worst queries section,
runnning eneperf using a reqlogparsed file against your Dgraph ...
Thanks for helping me. I got the reason for high memory utilization. it is due to wild card enabled for many dimensions and properties.
Edited by: Sunil N on Oct 22, 2012 9:13 AM