[
https://issues.apache.org/jira/browse/OAK-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Marchi updated OAK-1379:
---------------------------------
Attachment: ACLBenchmark-1.0-SNAPSHOT.zip
Simple JSP files we were using for our bulk data creation.
Run the following:
1.) /content/playground/benchmarkACL/prepPages/createUsers.html
2.) /content/playground/benchmarkACL/prepPages/method1.html
It will print the time for each iteration of the for loop in stdout.log
> Group membership and ACL assignment takes more time with mongodb and with crx2
> ------------------------------------------------------------------------------
>
> Key: OAK-1379
> URL: https://issues.apache.org/jira/browse/OAK-1379
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 0.15
> Environment: Centos 6x64
> Reporter: Nicholas Marchi
> Attachments: ACLBenchmark-1.0-SNAPSHOT.zip, load15mongovscrx2.jpg
>
>
> We were creating some data for a performance test and we noticed that our
> script took significantly longer to run with mongomk than with crx2.
> The scenario we are running looks like this:
> 1.) Create x users, x groups and x resources.
> 2.) Add n users to a group and then add an access control entry for that
> group to resource #n.
> What we found was that it took significantly longer to perform this action
> with mongomk than it did using crx2.
> For the record both tests were performed on indentical systems (CentOS6x64
> with 16gb ram) running load15, using either the crx3mongo, or crx2 run modes.
> The scenario wasn't designed as a performance test, we were just bulk
> creating test data, I just happened to print out the time with each update
> and noticed that they were very different between crx3mongo and crx2.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
