[
https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241320#comment-13241320
]
Antonio Sanso edited comment on SLING-2311 at 3/29/12 3:42 PM:
---------------------------------------------------------------
Adding new test case covering the scenario discussed in [0] sling:alias support.
It tests node having 1000 children and resource not found.
Here the outcome of the test with sling:alias support enabled (time in ms)
min 10% 50% 90%
max
jcr.resource-2.0.11 51 57 76 263 546
and with sling:alias support disabled
min 10% 50% 90%
max
jcr.resource-2.0.11 0 0 0 1 48
[0] http://sling.markmail.org/message/mlbw237hchhcyv6s
was (Author: asanso):
Adding new test case covering the scenario discussed in [0] sling:alias
support.
It tests node having 1000 children and resource not found.
Here the outcome of the test with sling:alias support enabled
jcr.resource-2.0.11 51 57 76 263 546
and with sling:alias support disabled
jcr.resource-2.0.11 0 0 0 1 48
[0] http://sling.markmail.org/message/mlbw237hchhcyv6s
> Sling Performance Testing tool
> ------------------------------
>
> Key: SLING-2311
> URL: https://issues.apache.org/jira/browse/SLING-2311
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Antonio Sanso
> Assignee: Carsten Ziegeler
> Priority: Minor
> Attachments: ResolveWithManyAliasTest.java, SLING-2311-patch.txt
>
>
> As described/discussed in [0] it would be nice to have a performance test
> tool in Sling .
> This can be useful in different situations (e.g. micro benchmarks of a
> feature and so on).
> Patch to follow
> [0] http://sling.markmail.org/message/bz44im7aqeae4r57
--
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
