Thanks Toke, After sorting with Self Time(CPU) I got that the FSDirectory$FSIndexOutput$1.write() is taking much of CPU time, so the bottleneck now is the IO of the hard drive?
https://drive.google.com/open?id=0BwLcshoSCVcdb2I4U1RBNnI0OVU On Tue, Mar 14, 2017 at 4:19 PM, Toke Eskildsen <t...@kb.dk> wrote: > On Tue, 2017-03-14 at 11:51 +0200, Mahmoud Almokadem wrote: > > Here is the profiler screenshot from VisualVM after upgrading > > > > https://drive.google.com/open?id=0BwLcshoSCVcddldVRTExaDR2dzg > > > > the jetty is taking the most time on CPU. Does this mean, the jetty > > is the bottleneck on indexing? > > You need to sort on and look at the "Self Time (CPU)" column in > VisualVM, not the default "Self Time", to see where the power is used. > The default is pretty useless for locating hot spots. > > - Toke Eskildsen, Royal Danish Library >
