ElasticSearch Java performance

Hi Marevol,

In my previous email I mentioned that in my last installation of FESS and ElasticSearch on a virtualized Windows 2008 server I have performance problems since Java running by ElasticSearch uses almost all available CPU.
I have tried looking for similar situations caused by ElasticSearch but there doesn’t seem to be much clarity on the possible causes and solutions.
Perhaps your experience could suggest some way to go to arrive at a solution (I also tried to completely delete the indexes and recreate them).

Many thanks

I think you need to configure proper Java heap memory and crawler settings for your environment and find a bottleneck on your resource first. Our commercial support will help it :slight_smile: