> After it is done, I cache the results, but the initial hit is bad.
>
> Any help would be much appreciated.
> Sdeck
>
>
>
>
--
View this message in context:
http://www.nabble.com/Speed-of-grouped-queries-tf2910499.html#a8285283
Sent from the Lucene - Java Users mailing li
create 1 HitSetCollector (I rolled my own
>> bitsetcollector)
>> and just run searches with it. I just get crapped on when it does that
>> genre search. I wish there was an easier way to aggregate all of those
>> documents together from all of those searches. After it
age in context:
http://www.nabble.com/Speed-of-grouped-queries-tf2910499.html#a8132099
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Speed-of-grouped-queries-tf2910499.html#a8147174
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
omitting norms and the term dictionary (from 2005):
>
> <http://www.nabble.com/Memory-Usage-tf523535.html>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this mes
Hi Scott,
sdeck wrote:
> I guess, any ideas why I would run out of heap memory by combining all of
> those boolean queries together and then running the query? What is happening
> in the background that would make that occur? Is it storing something in
> memory, like all of the common terms or som
le, how do actors, movies and genres relate to your documents?
>>> Do you have some external source(s) of information (i.e. external to
>>> your Lucene index) that relate actors to movies? And movies to genres?
>>>
>>> If actors, movies and genres are supposed to be a metaphor for what
>>> you're
Hi Scott,
sdeck wrote:
> I can't combine each of the movie queries together into one, because I get a
> memory error because of how many clauses there are (setting the clause
> higher did not help)
Have you tried increasing the memory available to the JVM? Sun's JVM
takes an option "-Xmx" to cha
at you're trying to "do".
>
> Steve
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
&g
While we're talking movies etc - did anyone else have a stab at the Netflix
prize using Lucene? ( http://www.netflixprize.com/ )
I did get onto the leaderboard (briefly) using a Lucene-based solution which
involved loading all 100 million movie reviews into a single RAMDirectory for
fast proc
Hi Sdeck,
sdeck wrote:
> The query for collecting a specific actor is around 200-300 milliseconds,
> and the movie one, that actually queries each actor, takes roughly 500-700
> milliseconds. Yet, for a genre, where you may have 50-100 movies, it takes
> 500 milliseconds*# of movies
I'm having tr
wish there was an easier way to aggregate all of those
documents together from all of those searches. After it is done, I cache
the results, but the initial hit is bad.
Any help would be much appreciated.
Sdeck
--
View this message in context:
http://www.nabble.com/Speed-of-grouped-queries
12 matches
Mail list logo
