lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-997) Add search timeout support to Lucene
Date Sat, 15 Dec 2007 21:57:43 GMT


Doron Cohen commented on LUCENE-997:

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.
Is this really faster than calling System.currentTimeMillis()?
I quick searched but found no references supporting this. 
This one says the opposite:
Because if this is not the case, you could do without the TimerThread?

> Add search timeout support to Lucene
> ------------------------------------
>                 Key: LUCENE-997
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>            Reporter: Sean Timm
>            Priority: Minor
>         Attachments:, 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.

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:
For additional commands, e-mail:

View raw message