[
https://issues.apache.org/jira/browse/JENA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418155#comment-13418155
]
Andy Seaborne commented on JENA-256:
------------------------------------
I have run your example code with and without the write batching optimization:
(6111, 6144, 6125) vs (21320, 21815, 22079)
The optimized version is using the overnight build of July 18/19.
The unoptimized version is current code base with write batch size set to zero.
Setup: Ubuntu 12.04, Oracle java 6 and Oracle java 7.
With batched writes:
All 100 write operations wrote 5250 triples and took 7388ms
Total opening transaction time was 152ms
Total commit transaction time was 6111ms
All 100 write operations wrote 5250 triples and took 7392ms
Total opening transaction time was 150ms
Total commit transaction time was 6144ms
All 100 write operations wrote 5250 triples and took 7415ms
Total opening transaction time was 148ms
Total commit transaction time was 6125ms
Without batched writes:
All 100 write operations wrote 5250 triples and took 22869ms
Total opening transaction time was 184ms
Total commit transaction time was 21320ms
All 100 write operations wrote 5250 triples and took 23327ms
Total opening transaction time was 187ms
Total commit transaction time was 21815ms
All 100 write operations wrote 5250 triples and took 23581ms
Total opening transaction time was 196ms
Total commit transaction time was 22079ms
Also - the numbers of several runs are much more consistent that
> 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
