>> multiple connections
>> from a connection pool.
>
> I understand. It's probably not a good idea to open a new connection
> for each operation, because for some databases opening a connection
> takes very long. I have implemented a simple pool (with maxSize) now,
> I like to test it a little befo
Hi,
> multiple connections
> from a connection pool.
I understand. It's probably not a good idea to open a new connection
for each operation, because for some databases opening a connection
takes very long. I have implemented a simple pool (with maxSize) now,
I like to test it a little before com
Hi Jukka.
What about JCR-314, 935 (which you mentioned) and 1148, issues related with the
fine grained
locking?
We've been testing the fix I proposed for JCR-1148 in the JCR-935 comments for
some time now and
haven't had any NPE due to it.
Regards,
Esteban Franqueiro
[EMAIL PROTECTED]
Notic
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547849
]
Przemo Pakulski commented on JCR-1253:
--
Notice, that I marked this improvement as MINOR, it does not affect overal
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547835
]
Thomas Mueller commented on JCR-1253:
-
Hi,
I have noticed the fonts are different in the images - did you run the
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Przemo Pakulski updated JCR-1253:
-
Attachment: single_checkin.JPG
> Allow to configure autoCommit mode for BundleDB PM to avoid extra
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Przemo Pakulski updated JCR-1253:
-
Attachment: small_change_log.JPG
> Allow to configure autoCommit mode for BundleDB PM to avoid extr
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Przemo Pakulski updated JCR-1253:
-
Attachment: (was: small_change_log.html)
> Allow to configure autoCommit mode for BundleDB PM t
[
https://issues.apache.org/jira/browse/JCR-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Przemo Pakulski updated JCR-1253:
-
Attachment: small_change_log.html
store with small change log
> Allow to configure autoCommit mode
Allow to configure autoCommit mode for BundleDB PM to avoid extra overhead when
working in non clustered environment
Key: JCR-1253
URL: https://is
It's hard to say exact numbers, there are to many variables (network
speed/latency, db server type, jdbc driver, change log size).
For sure it means 2 extra network calls, which could be easily avoided.
See attached example screen from JProfiler using MSSQL server, and small
change logs, overhe
Hi,
> What do you mean by clustered env.
Jackrabbit cluster
> use autoCommit mode only in 'clustered environment'
> to avoid extra overhead in simple
> deployment.
Did you test how much overhead it is? Do you have a test case that
shows that performance can be improved by changing it? If yes, h
What do you mean by clustered env. exactly : Jackrabbit cluster,
database cluster, other ? Btw, simple db persistence manager don't use
autocommit mode, does it mean that it will not work in clustered env ?
Myabe we should add parameter to BundleDB PMs, and use autoCommit mode
only in 'cluster
[
https://issues.apache.org/jira/browse/JCR-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved JCR-1252.
-
Resolution: Fixed
Fixed in revision 600468
> BundleFsPersistenceManager: remove deprecated setting
BundleFsPersistenceManager: remove deprecated settings
--
Key: JCR-1252
URL: https://issues.apache.org/jira/browse/JCR-1252
Project: Jackrabbit
Issue Type: Improvement
Components:
15 matches
Mail list logo
