How would we know where the problem is? It's your custom implementation. And it's your own documents, so we don't know field sizes/etc. And it's your own metric (ok, Indian metric, but lacs are fairly unknown outside of India).
Seriously though, have you tried using any memory profilers and running with/without your EFF implementation or with just dummy return result? Java 8 has some new FlightRecorder and other tools built-in. That would tell you where the leak/usage might be. I think this kind of question, you need to really dig deep in yourself first. Have you tried using EFF but a primitive one that does not load anything from file? Is there performance impact? If not, then the issue is most likely in your code. Maybe it does not shutdown properly when Indexer is reloaded or similar. Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, Jul 3, 2014 at 12:23 PM, Kamal Kishore Aggarwal <kkroyal....@gmail.com> wrote: > Any replies ?? > > > On Sat, Jun 28, 2014 at 5:34 PM, Kamal Kishore Aggarwal < > kkroyal....@gmail.com> wrote: > >> Hi Team, >> >> I have recently implemented EFF in solr. There are about 1.5 >> lacs(unsorted) values in the external file. After this implementation, the >> server has become slow. The solr query time has also increased. >> >> Can anybody confirm me if these issues are because of this implementation. >> Is that memory does EFF eats up? >> >> Regards >> Kamal Kishore >>
