[ 
https://issues.apache.org/jira/browse/LUCENE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Miller updated LUCENE-1844:
--------------------------------

    Attachment: FastCnstScoreQTest.patch

TestCustomScoreQuery appears to be the longest test - its about a minute or 
worse.

The test can be set to log output, where it may display explain info - on many, 
many loops this explain info is calculated, only to be *not* logged because 
logging is off by default.

1. Excessive explain calculations turned off if logging is off.

In a logging call, QueryUtils.check(query, searcher) is called (overall ends up 
in a tight loop) - but it keeps getting called with the same query objects and 
the same searcher.

2. QueryUtils.check(query, searcher) moved out of loop and only tested once for 
each query.


Test from approx 60 seconds to approx 5 seconds.

> Speed up junit tests
> --------------------
>
>                 Key: LUCENE-1844
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1844
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Mark Miller
>         Attachments: FastCnstScoreQTest.patch, hi_junit_test_runtimes.png
>
>
> As Lucene grows, so does the number of JUnit tests. This is obviously a good 
> thing, but it comes with longer and longer test times. Now that we also run 
> back compat tests in a standard test run, this problem is essentially doubled.
> There are some ways this may get better, including running parallel tests. 
> You will need the hardware to fully take advantage, but it should be a nice 
> gain. There is already an issue for this, and Junit 4.6, 4.7 have the 
> beginnings of something we might be able to count on soon. 4.6 was buggy, and 
> 4.7 still doesn't come with nice ant integration. Parallel tests will come 
> though.
> Beyond parallel testing, I think we also need to concentrate on keeping our 
> tests lean. We don't want to sacrifice coverage or quality, but I'm sure 
> there is plenty of fat to skim.
> I've started making a list of some of the longer tests - I think with some 
> work we can make our tests much faster - and then with parallelization, I 
> think we could see some really great gains.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to