You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2008/05/09 12:33:18 UTC

Performance testing in jcr2spi

Hi,

QueryTest in jcr2spi runs ten queries with different namespace
mappings and outputs (in System.out) the millisecond timing of the
queries:

    Running org.apache.jackrabbit.jcr2spi.query.TestAll
    Executed 10 queries in 18 ms
    Time per query: 1 ms
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec

Do we need those measurements for something, or should we just drop them?

For performance testing I would suggest that we either set clear
performance goals that can be used as assertions
(assertTrue(timePerQuery < 5)) or use some other way than
System.out.print to report them. IMHO even the JUnit report for
QueryTest is more useful for performance reporting as it's at least
structured information:

    <testcase time="0.034" name="testRemappedNamespace"/>

BR,

Jukka Zitting

Re: Performance testing in jcr2spi

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Fri, May 9, 2008 at 3:16 PM, Marcel Reutegger
<ma...@gmx.net> wrote:
>  that's just a left over. I forgot to remove the System.out calls when I
> committed the test.
>
>  I'll remove the calls.

OK, thanks!

BR,

Jukka Zitting

Re: Performance testing in jcr2spi

Posted by Marcel Reutegger <ma...@gmx.net>.

Hi,

that's just a left over. I forgot to remove the System.out calls when I 
committed the test.

I'll remove the calls.

regards
  marcel

Jukka Zitting wrote:
> Hi,
> 
> QueryTest in jcr2spi runs ten queries with different namespace
> mappings and outputs (in System.out) the millisecond timing of the
> queries:
> 
>     Running org.apache.jackrabbit.jcr2spi.query.TestAll
>     Executed 10 queries in 18 ms
>     Time per query: 1 ms
>     Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec
> 
> Do we need those measurements for something, or should we just drop them?
> 
> For performance testing I would suggest that we either set clear
> performance goals that can be used as assertions
> (assertTrue(timePerQuery < 5)) or use some other way than
> System.out.print to report them. IMHO even the JUnit report for
> QueryTest is more useful for performance reporting as it's at least
> structured information:
> 
>     <testcase time="0.034" name="testRemappedNamespace"/>
> 
> BR,
> 
> Jukka Zitting
>