[
https://issues.apache.org/jira/browse/JENA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418609#comment-13418609
]
Simon Helsen commented on JENA-256:
-----------------------------------
ok, so I tried the drop, but that didn't make a difference. Then I realized,
looking at the code that I was probably running in mapped mode which, on
Windows is shaky (and known to be slower), so I explicitly changed to use
direct mode. The first run went fine (and fast), but the second run failed with
the following exception (systematically):
Exception in thread "main" com.hp.hpl.jena.tdb.base.block.BlockException:
BlockAccessBase: Bounds exception:
C:\Temp\jenaTests\indexTestLocation\GSPO.dat: (40,40)
at
com.hp.hpl.jena.tdb.base.file.BlockAccessBase.check(BlockAccessBase.java:107)
at
com.hp.hpl.jena.tdb.base.file.BlockAccessBase.check(BlockAccessBase.java:114)
at
com.hp.hpl.jena.tdb.base.file.BlockAccessDirect.write(BlockAccessDirect.java:85)
at
com.hp.hpl.jena.tdb.base.file.BlockAccessDirect.overwrite(BlockAccessDirect.java:104)
at
com.hp.hpl.jena.tdb.base.block.BlockMgrFileAccess.overwrite(BlockMgrFileAccess.java:102)
at
com.hp.hpl.jena.tdb.base.block.BlockMgrWrapper.overwrite(BlockMgrWrapper.java:89)
at
com.hp.hpl.jena.tdb.base.block.BlockMgrSync.overwrite(BlockMgrSync.java:90)
at
com.hp.hpl.jena.tdb.base.block.BlockMgrCache.overwrite(BlockMgrCache.java:206)
at
com.hp.hpl.jena.tdb.transaction.JournalControl.replay(JournalControl.java:305)
at
com.hp.hpl.jena.tdb.transaction.JournalControl.recoverSegment(JournalControl.java:175)
at
com.hp.hpl.jena.tdb.transaction.JournalControl.recoverFromJournal(JournalControl.java:128)
at
com.hp.hpl.jena.tdb.StoreConnection._makeAndCache(StoreConnection.java:237)
at com.hp.hpl.jena.tdb.StoreConnection.make(StoreConnection.java:196)
at
com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.<init>(DatasetGraphTransaction.java:76)
at com.hp.hpl.jena.tdb.sys.TDBMakerTxn._create(TDBMakerTxn.java:49)
at
com.hp.hpl.jena.tdb.sys.TDBMakerTxn.createDatasetGraph(TDBMakerTxn.java:37)
at
com.hp.hpl.jena.tdb.TDBFactory._createDatasetGraph(TDBFactory.java:104)
at com.hp.hpl.jena.tdb.TDBFactory.createDatasetGraph(TDBFactory.java:73)
at com.hp.hpl.jena.tdb.TDBFactory.createDataset(TDBFactory.java:52)
at com.hp.hpl.jena.tdb.TDBFactory.createDataset(TDBFactory.java:48)
at
com.ibm.jena.test.PerformanceRegressionTest.main(PerformanceRegressionTest.java:54)
It is reproducible and the only thing I did was add the following static block:
static {
ARQ.getContext().set(SystemTDB.symFileMode, "direct");
}
Can you reproduce this?
> Significant performance regression (TDB?) on 2.7.1 RC compared to May 15 build
> ------------------------------------------------------------------------------
>
> Key: JENA-256
> URL: https://issues.apache.org/jira/browse/JENA-256
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB
> Affects Versions: Jena 2.7.1
> Environment: Windows 7, 64 bit, tested against 2.7.1 RC from June 9
> versus a build from May 15
> Reporter: Simon Helsen
> Assignee: Andy Seaborne
> Priority: Critical
> Fix For: TDB 0.9.3
>
> Attachments: 271May15Output1.txt, 271May15Output2.txt,
> 271May15Output3.txt, 271May15Output4.txt, 271RCOutput1.txt, 271RCOutput2.txt,
> 271RCOutput3.txt, 271RCOutput4.txt, PerformanceRegressionTest.java
>
>
> See also
> http://mail-archives.apache.org/mod_mbox/jena-dev/201206.mbox/%3C4FD9F19E.3080904%40bristol.ac.uk%3E
> I was able to reproduce the performance regression with an isolated test
> scenario. So I recreated the components ARQ, CORE, IRI, and TDB with the SVN
> state of May 15 9 (so svn update -r {2012-05-15} and then svn clean install)
> I then created a simple test program (attached as
> PerformanceRegressionTest.java) which I ran 4 times in a row for each version
> of Jena. Note that I deleted the TDB directory after the first 4 runs before
> using the other Jena version. Attached are the files with the output. The
> regression is obvious
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
