[ https://issues.apache.org/jira/browse/JENA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419024#comment-13419024 ]
Andy Seaborne commented on JENA-256: ------------------------------------ You can have separate non-nested transactions by doing: Dataset dataset = TDBFactory.createDataset(location); Dataset dataset1 = TDBFactory.createDataset(location); and use one dataset as a reader and one as the writer. Just don't start two overlapping writes on two different datasets on the same thread as a write requests is queued until it can be granted. > 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