It doesn't sound like you have much of an understanding of java's garbage collection. You might read http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/gc01/index.html to get a better understanding of how it works and why you're seeing different levels of memory utilization at any given point in time. The thing to note is that while doing anything java applications are going to create objects that reside in the java heap and take up space. After a while those objects are which are no longer in use and orphaned by their creating objects get collected by the jvm which lowers the amount of heap used. In most cases you shouldn't expect memory usage in a jvm to be static unless it's sitting around idle.
Thanks, Greg On Mar 5, 2014, at 11:58 AM, sweety <sweetyshind...@yahoo.com> wrote: > Now i have batch indexed, with batch of 250 documents.These were the results. > After 7,000 documents, > Qtime: 46894, System time : 00:00:55.9384892 > JVM memory : 249.02mb, 24.8% > This shows quite a reduction in timing. > > After 70,000 documents, > Qtime: 480435, System time : 00:09:29.5206727 > System memory : 82.8%, 2.90gb > JVM memory : 82% , 818.06mb //Here, the memory usage has increased, though > the timing has reduced. > > After disabling softcommit and tlog, for 70,000 contracts. > Qtime: 461331, System time : 00:09:09.7930326 > JVM Memory : 62.4% , 623.42mb. //Memory usage is less. > > What causes this memory usage to change, if the data to be indexed is same? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/to-reduce-indexing-time-tp4121391p4121441.html > Sent from the Solr - User mailing list archive at Nabble.com.
