You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Mark Miller (Jira)" <ji...@apache.org> on 2019/09/26 15:48:00 UTC

[jira] [Commented] (SOLR-13796) Fix Solr Test Performance

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

Mark Miller commented on SOLR-13796:
------------------------------------

I would also like to start enforcing limits on non Nightly tests - runtimes that exceed a certain fairly low threshold will start failing tests and suggesting alternatives or Nightly. Close times of critical components will also be instrumented and tracked and limited for reasonable times.

There is also a new, consistent, fast way to close objects safely that does this close tacking and has also sped up object lifecycle quite a bit even where we already tried to things fast.

> Fix Solr Test Performance
> -------------------------
>
>                 Key: SOLR-13796
>                 URL: https://issues.apache.org/jira/browse/SOLR-13796
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Major
>
> I had kind of forgotten, but while working on Starburst I had realized that almost all of our tests are capable of being very fast and logging 10x less as a result. When they get this fast, a lot of infrequent random fails become frequent and things become much easier to debug. I had fixed a lot of issue to make tests pretty damn fast in the starburst branch, but tons of tests where still ignored due to the scope of changes going on.
> A variety of things have converged that have allowed me to absorb most of that work and build up on it while also almost finishing it.
> This will be another huge PR aimed at addressing issues that have our tests often take dozens of seconds to minutes when they should take mere seconds or 10.
> As part of this issue, I would like to move the focus of non nightly tests towards being more minimal, consistent and fast.
> In exchanged, we must put more effort and care in nightly tests. Not something that happens now, but if we have solid, fast, consistent non Nightly tests, that should open up some room for Nightly to get some status boost.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org