[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Timm updated LUCENE-997:
-----------------------------
Attachment: TimerThreadTest.java
The TimerThreadTest illustrates the accuracy of the TimerThread under load. On
my 2GHz Xeon 4 CPU dual core RH AS 4 Linux box, it get a 20% difference between
the TimerThread implementation and System.currentTimeMillis() and is
independent of load.
java TimerThreadTest 8
[...]
10010 12020 [...]
With my single core single CPU Windows XP laptop I see a 20% difference at
load, but when adding additional threads, I see an increasing difference.
java TimerThreadTest 0
[...]
10000 11819 [...]
java TimerThreadTest 2
[...]
10040 18890 [...]
> 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: HitCollectorTimeoutDecorator.java,
> LuceneTimeoutTest.java, LuceneTimeoutTest.java, MyHitCollector.java,
> timeout.patch, timeout.patch, timeout.patch, TimerThreadTest.java
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
