lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Harwood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-1720) TimeLimitedIndexReader and associated utility class
Date Mon, 17 Aug 2009 23:06:15 GMT

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

Mark Harwood updated LUCENE-1720:
---------------------------------

    Attachment: ActivityTimeMonitor.java

Had another run at ActivityTimeMonitor tonight and rationalised the code based on earlier
comments. It should now cater for multiple simultaneous timeouts more cleanly.

I'm concentrating on robustness with this currently - there's a TODO comment in the code that
captures a small remaining inefficiency in iterating through all threads' data rather than
using some form of time-sorted list. There was a suggestion in the earlier Jira comments re
TreeMap might be a simple alternative but see my Java code comments as to why this is unlikely
to work. Optimising this is likely to require the introduction of yet another data structure
but this will add a runtime cost to maintain it - a cost I'm not sure is justified.



> TimeLimitedIndexReader and associated utility class
> ---------------------------------------------------
>
>                 Key: LUCENE-1720
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1720
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Index
>            Reporter: Mark Harwood
>            Assignee: Mark Harwood
>            Priority: Minor
>         Attachments: ActivityTimedOutException.java, ActivityTimeMonitor.java, ActivityTimeMonitor.java,
TestTimeLimitedIndexReader.java, TimeLimitedIndexReader.java
>
>
> An alternative to TimeLimitedCollector that has the following advantages:
> 1) Any reader activity can be time-limited rather than just single searches e.g. the
document retrieve phase.
> 2) Times out faster (i.e. runaway queries such as fuzzies detected quickly before last
"collect" stage of query processing)
> Uses new utility timeout class that is independent of IndexReader.
> Initial contribution includes a performance test class but not had time as yet to work
up a formal Junit test.
> TimeLimitedIndexReader is coded as JDK1.5 but can easily be undone.

-- 
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message