Provide utility for handling large number of child nodes/properties
---
Key: JCR-2688
URL: https://issues.apache.org/jira/browse/JCR-2688
Project: Jackrabbit Content Repository
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated JCR-2688:
---
Attachment: JCR-2688.patch
Proposed patch
Example usage:
// Create a new TreeManager instance
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893129#action_12893129
]
Michael Dürig commented on JCR-2688:
Open questions:
- Currently these utility classes
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893130#action_12893130
]
Thomas Mueller edited comment on JCR-2688 at 7/28/10 6:27 AM:
--
I
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893130#action_12893130
]
Thomas Mueller commented on JCR-2688:
-
That about a test dependency?
Provide utility
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893171#action_12893171
]
Justin Edelson commented on JCR-2688:
-
I would use a test dependency. Placing the tests
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893177#action_12893177
]
Michael Dürig commented on JCR-2688:
Maven seems to fine with jackrabbit-core as test
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893181#action_12893181
]
Justin Edelson commented on JCR-2688:
-
Maven seems to fine with jackrabbit-core as test
hi,
jackrabbit currently indeed serializes writes on the persistence
level. as a workaround you could batch multiple writes into a single
session save. though, I'm not sure if that's an option in your case.
regards
marcel
On Wed, Jul 28, 2010 at 11:25, smjain jain...@gmail.com wrote:
Hi All,
Hi,
Are you sure the problem is concurrency and not performance? Are
you sure that the persistence manager you use does support higher
write throughput? What persistence manager do you use, and what is the
write throughput you see, and what do you need?
Regards,
Thomas
Hi,
The problem is performance . Thats based on concurrent writes we are doing.
So if I see the design of jackrabbit and as much I make out of it is
that the Write lock is acquired at the SharedItemStateManager level
which is above PersistanceManager.
We tried changing to DB persistance manager
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893193#action_12893193
]
Michael Dürig commented on JCR-2688:
So I see four option for the unit tests:
1. Move
Hi,
Do you use Day CRX / CQ? If yes, I suggest to use the Day support.
Regards,
Thomas
Sure..
We are already going through them. I just wanted to make sure if we
have some kind of configuration to allow parallel writes in
jackrabbit if we write to different
parts of repository..What I am getting here is that writes will be
serialized due to a Single Write lock
Thanks a lot
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893204#action_12893204
]
Alexander Klimetschek commented on JCR-2688:
1. is the right way: if jackrabbit's
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893208#action_12893208
]
Michael Dürig commented on JCR-2688:
Yes technically 1. is the right way... However I
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893209#action_12893209
]
Justin Edelson commented on JCR-2688:
-
5. Leave the unit tests in jcr-commons and use
[
https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893212#action_12893212
]
Michael Dürig commented on JCR-2688:
5. means basically reimplementing JCR...
6. is more
Hi,
What I am getting here is that writes will be
serialized due to a Single Write lock
For scalability, you also need scalable hardware. Just using multiple
threads will not improve performance if all the data is then stored on
the same disk.
Regards,
Thomas
Sure..
But with 100 concurrent threads I guess we should not be looking for
big hardware anyways.
Also if we cluster the repository I guess still we deal with a global
lock across nodes..
So not sure how much we gain
Thanks
Shashank
On Wed, Jul 28, 2010 at 9:06 PM, Thomas Müller
Hello,
sorry, I know, ist the wrong mailinglist, but i am actually not member of
the users list.
Perhaps someone would and could answer me.
Till now I use XPATH for querying the repository, but now I want to change
to SQL2. The samples in the test case explains the basics, but I didnt
[
https://issues.apache.org/jira/browse/JCR-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893475#action_12893475
]
Graeme Steyn commented on JCR-2664:
---
Tha patch file appears as an attachement to this case,
22 matches
Mail list logo
