[
https://issues.apache.org/jira/browse/JENA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295185#comment-13295185
]
Simon Helsen commented on JENA-256:
-----------------------------------
And while this is probably expected, the time is lost in the commit. I am
attaching an updated version which keeps the dataset creation outside and adds
a few more numbers. Here are the summaries of 3 subsequent tests, first on the
RC and then on the May 15 build (and all on Sun JRE 6):
RC - test 1:
All 100 write operations wrote 5250 triples and took 7548ms
Total opening transaction time was 380ms
Total commit transaction time was 5647ms
RC - test 2:
All 100 write operations wrote 5250 triples and took 12040ms
Total opening transaction time was 387ms
Total commit transaction time was 10081ms
RC - test 3:
All 100 write operations wrote 5250 triples and took 11761ms
Total opening transaction time was 377ms
Total commit transaction time was 10061ms
May 15 - test 1:
All 100 write operations wrote 5250 triples and took 4317ms
Total opening transaction time was 384ms
Total commit transaction time was 2853ms
May 15 - test 2:
All 100 write operations wrote 5250 triples and took 5410ms
Total opening transaction time was 399ms
Total commit transaction time was 3672ms
May 15 - test 3:
All 100 write operations wrote 5250 triples and took 5266ms
Total opening transaction time was 384ms
Total commit transaction time was 3405ms
> 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
> Priority: Critical
> 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
