I had it with an SSD, but fsync could be an issue anyway. It could also be an JDK implementation 'issue' for linux JDK. That's why I wonder if it's reproduceable by anybody else.
Regards Felix 2015-03-24 8:03 GMT+01:00 Stefan Seelmann <[email protected]>: > I can't reproduce this on my laptop (which has an SSD). But I think I > saw that before on a machine with spindle HDD. Maybe it has to do with > too many fsync when writing to disk? > > Kind Regards, > Stefan > > > On 03/24/2015 06:44 AM, Felix Knecht wrote: > > Hi > > > > Just for the record. Looks like this is the test taking much longer in > > JDK 1.7: > > > > Running org.apache.directory.mavibot.btree.PersistedBTreeBrowseTest > > Browse Forward for 9 = 4320 > > Browe backward for 9 = 5125 > > Tests run: 25, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 235.79 > > sec - in org.apache.directory.mavibot.btree.PersistedBTreeBrowseTest > > > > whilst in JDK 1.8: > > Running org.apache.directory.mavibot.btree.PersistedBTreeBrowseTest > > Browse Forward for 9 = 3861 > > Browe backward for 9 = 4990 > > Tests run: 25, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 16.635 > > sec - in org.apache.directory.mavibot.btree.PersistedBTreeBrowseTest > > > > Regards > > Felix > >
