[jira] Commented: (LUCENE-997) Add search timeout support to Lucene

["Doron Cohen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552143 ] 

Doron Cohen commented on LUCENE-997:
------------------------------------

{quote}
TimerThread provides a pseudo-clock service to all searching threads, 
so that they can count elapsed time with less overhead than repeatedly 
calling System.currentTimeMillis. A single thread should be created to 
be used for all searches.
{quote}
Is this really faster than calling System.currentTimeMillis()?
I quick searched but found no references supporting this. 
This one says the opposite:
  http://www.devx.com/Java/Article/28685
Because if this is not the case, you could do without the TimerThread?


> Add search timeout support to Lucene
> ------------------------------------
>
>                 Key: LUCENE-997
>                 URL: https://issues.apache.org/jira/browse/LUCENE-997
>             Project: Lucene - Java
>          Issue Type: New Feature
>            Reporter: Sean Timm
>            Priority: Minor
>         Attachments: LuceneTimeoutTest.java, timeout.patch, timeout.patch
>
>
> This patch is based on Nutch-308. 
> This patch adds support for a maximum search time limit. After this time is exceeded, the search thread is stopped, partial results (if any) are returned and the total number of results is estimated.
> This patch tries to minimize the overhead related to time-keeping by using a version of safe unsynchronized timer.
> This was also discussed in an e-mail thread.
> http://www.nabble.com/search-timeout-tf3410206.html#a9501029

-- 
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