[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770033#action_12770033
]
Thomas Mueller commented on JCR-1456:
-------------------------------------
Strange is that Connection.getAutoCommit() is called so much (maybe 50% of all
JDBC method calls). Sometimes it is called 4 times in a row, without any other
JDBC calls in between. It's not a problem for most databases (specially
embedded), but I wonder why it is called so much and if this could be avoided.
I just tested H2 embedded. I don't know why H2 got slower in your case, maybe
because you set the trace level to the maximum, or because you have used the
server mode (I used embedded and disabled the trace output).
127 seconds with trunk
131 seconds with JCR-1456
Maven 2.0.9, 1.5.0_20, Mac OS 10.5.8
Unrelated to JCR-1456: I had to disable the H2 shutdown hook because one of
tests doesn't seem to close the repository correctly, so that Jackrabbit
executes database statements in a shutdown hook. This only happens in the
trunk, not in JCR-1456.
> Database connection pooling
> ---------------------------
>
> Key: JCR-1456
> URL: https://issues.apache.org/jira/browse/JCR-1456
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Fix For: 2.0.0
>
> Attachments: 777490.patch, dbcp.patch, dbcp.patch,
> JCR-1456-performance-trunk-test-setup.patch, JCR-1456-performance.txt,
> JCR-1456.patch, patch-1456-1.txt, patch-1456-2.txt, patch-1456-3.txt
>
>
> Jackrabbit should use database connection pools instead of a single
> connection per persistence manager, cluster journal, or database data store.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
