On 3/5/2014 7:47 AM, sweety wrote: > Before indexing , this was the memory layout, > > System Memory : 63.2% ,2.21 gb > JVM Memory : 8.3% , 81.60mb of 981.38mb > > I have indexed 700 documents of total size 12MB. > Following are the results i get : > Qtime: 8122, System time : 00:00:12.7318648 > System Memory : 65.4% ,2.29 gb > JVM Memory : 15.3% , 148.32mb of 981.38mb > > After indexing 7,000 documents, > Qtime: 51817, System time : 00:01:12.6028320 > System Memory : 69.4% 2.43Gb > JVM Memoery : *26.5%* , 266.60mb > > After indexing 70,000 documents of 1200mb size, this are the results : > Qtime: 511447, System time : 00:11:14.0398768 > System memory : 82.7% , 2.89Gb > JVM memory :* 11.8%* , 118.46mb > > Here the JVM usage decreases as compared to 7000 doc, why is it so??
Ahmet already addressed your configuration and how to speed things up. Here's the answer to your memory question: The simple fact is that during *all* of those tests, at least one of your heap memory pools will have reached maximum size and then been reduced by garbage collection. This memory graph from the jconsole shows what happens with Java heap memory: http://docs.oracle.com/javase/1.5.0/docs/guide/management/jconsole.html#memory After indexing, your final example was simply at one of the low points in the graph, but the other examples were at a higher point. Thanks, Shawn
