You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2012/08/27 22:17:08 UTC

[jira] [Commented] (SLING-2311) Sling Performance Testing tool

    [ https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442681#comment-13442681 ] 

Justin Edelson commented on SLING-2311:
---------------------------------------

I've added this in r1377819. Thanks for the contribution.

I had to make a number of modifications. Chiefly is that since these tests rely on internal methods which change from release to release, the logic for constructing a ResourceResolver is encapsulated into a helper class (called TestHelper - don't love the name, but we can change it).

Added more scenarios for the tests included based on node size, e.g. 1000 vanity paths, 5000 vanity paths, etc.

One thing that I couldn't figure out is why a JcrResourceListener was being created, so I removed that bit. Antonio - please let me know if this needs to be there.

Tests can be run for JCR Resource Resolver 2.0.10, 2.1.0, and 2.1.1-SNAPSHOT (which I'm calling 2.2.0 for the sake of argument).

 
                
> 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: Justin Edelson
>            Priority: Minor
>         Attachments: ResolveWithManyAliasTest.java, ResolveWithManyVanityPath.png, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira