Hi Michael:
I took your program and benchmarked against my setup, here are some
numbers comparing to the other options:
Setup: 2M docs with only the id, indexed in various ways for each method
randomly selected 5 of the docids and do a lookup.
Comparing 3 methods:
1) load int[] from fi
On 10/20/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> I would think the typical use case would be you want all the
> "small" fields to be returned w/ the document and the large fields to
> be lazily loaded. I think it should be seamless to the user.
That may be a little too seamless. We want
[
https://issues.apache.org/jira/browse/LUCENE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536510
]
Digy commented on LUCENE-1029:
--
I think , the phrase
+ * Please note that the replacements performed by this filter w
[
https://issues.apache.org/jira/browse/LUCENE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-550:
---
Attachment: LUCENE-550_20071021_no_core_changes.txt
In this patch:
* Replaced all List with T[] as
John Wang wrote:
>
> Since all three methods loads docids into an int[], the lookup time is the
> same for all three methods, what's
> different are the load times:
>
> 1) 16.5 seconds, 43 MB
> 2) 590 milliseconds 32.5 MB
> 3) 186 milliseconds 26MB
Good analysis! Thanks for sharing th
