My problem was not how heavy it is, but if ist only used inside conditionals we should not mix it.
I have to mention: MacOSX JDK 1.7.0_10 crashed when nanotime went backwards... :-) See my mail and fix for this a few days ago. Happy JVM crashing! Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Michael McCandless [mailto:[email protected]] > Sent: Friday, January 04, 2013 5:37 PM > To: [email protected] > Subject: Re: svn commit: r1428947 - in > /lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/index: > IndexFileDeleter.java SegmentMerger.java > > On Fri, Jan 4, 2013 at 11:34 AM, Uwe Schindler <[email protected]> wrote: > > > System.nanoTime is a syscall and heavy on some O/S. The times are only > used when inforstream is enabled, so the calls to nanotime should only be > inside "if (infostream)" blocks. Some of them are outside this check. > > How heavy? As heavy as a Lucene merge? ;) > > OK ok, I'll move them under the if ... > > Mike McCandless > > http://blog.mikemccandless.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
