>>
>>
>> Query callDetailquery =
>> parser.parse(searchQuery);
>>
>> hits = is.searc
;>>>>>>> Search.it is used
>>>>>>>> >>>>> for all other searches.
>>>>>>>> >>>>>
>>>>>>>> >>>>> 5.I am using Lucene 2.2.0 version, in a WEB
>>>>>>>> Application
>>>>>>>> >>>>> which index 15 fields per document and Ind
gt;> >>>>> it fetches 600 records from the index store(5 direcories)
>>>>>>> >>>>>
>>>>>>> >>&g
>>>>>> >>>>>
>>>>>> >>>>> hossman wrote:
>>>>>> >>>>>>
>>>>>> >>>>>>
>>>>>> >>>>>> : I set IndexSearcher as the application Object after the
>>>>>> first
t;>
>>>>>> >>>>>> : I set IndexSearcher as the application Object after the
>>>>>> first
>>>>>> >>>>>> search.
>>>>>> >>>>>> ...
>>>>>> >&
;>> search.
>>>>> >>>>>>...
>>>>> >>>>>> : how can i reconstruct the new IndexSearcher for every hour to
>>>>> see
>>>>> >>>>>> the
>>>>> >>>>>> : updated records .
>>>>> >>>>>>
&g
>>>>>> i'm confused ... my understanding based on the comments you made
>>>> >>>>>> below
>>>> >>>>>> (in an earlier message) was that you already *were* constructing
>>>> a
>>>> >>>>>> new
>>>> >>>>&
t;> new
>>> >>>>>> IndexSearcher once an hour -- but every time you do that, your
>>> memory
>>> >>>>>> usage grows, and and that sometimes you got OOM Errors.
>>> >>>>>>
>>> >>>>>> if that's not what you s
;>> if that's not what you said, then i think you need to explain, in
>> >>>>>> detail,
>> >>>>>> in one message, exactly what your problem is. And don't assume we
>> >>>>>> understand anything -- tell us *EVERYTHING* (like, f
gt;>>>
>>>>>>>> if that's not what you said, then i think you need to explain, in
>>>>>>>> detail,
>>>>>>>> in one message, exactly what your problem is. And don't assume we
>>>>>>>&
oblem is. And don't assume we
>>>>>>> understand anything -- tell us *EVERYTHING* (like, for example, what
>>>>>>> the
>>>>>>> word "crore" means, how "searcherOne" is implemented, and the answer
>>>>&
(like, for example, what
> >>>>>> the
> >>>>>> word "crore" means, how "searcherOne" is implemented, and the answer
> >>>>>> to
> >>>>>> the specfic question i asked in my last message: does yo
re" means, how "searcherOne" is implemented, and the answer
>>>>>> to
>>>>>> the specfic question i asked in my last message: does your
>>>>>> application,
>>>>>> contain anywhere in it, any code that will close anyt
essage: does your
>>>>> application,
>>>>> contain anywhere in it, any code that will close anything
>>>>> (IndexSearchers
>>>>> or IndexReaders) ?
>>>>>
>>>>>
>>>>> : > : I use StandardAnalyzer.the records daily ranges from 5 crore to
> one
>>>> : > : time for all the searches. for an hour can i see the updated
>>>> records in
>>>> : > the
>>>> : > : indexstore by reinstantiating IndexSearcher object.but the
>>>> problem when
>>>> : > i
>>>
: > : indexstore by reinstantiating IndexSearcher object.but the problem
>>> when
>>> : > i
>>> : > : reinstantiate IndexSearcher ,my RAM memory gets appended.is there
>>> any
>>>
>>>
>>> : > IndexSearcher are you explicitly closing both
antiating IndexSearcher object.but the problem
>> when
>> : > i
>> : > : reinstantiate IndexSearcher ,my RAM memory gets appended.is there
>> any
>>
>>
>> : > IndexSearcher are you explicitly closing both the old IndexSearcher
>> as
>> :
t;
>
>
> -Hoss
>
>
> -----------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Java-Heap-
nded.is there any
>>
>> skimming hte code below, you are opening an IndexSearcher over a
>> MultiReader over 4 seperate IndexReaders ... when you instantiate a new
>> IndexSearcher are you explicitly closing both the old IndexSearcher as
>> well as all of 4 o
: I set IndexSearcher as the application Object after the first search.
...
: how can i reconstruct the new IndexSearcher for every hour to see the
: updated records .
i'm confused ... my understanding based on the comments you made below
(in an earlier message) was that you already *wer
the MultiReader?
>
> closing an IndexSearcher will only close the underlying Reader if it
> opened it .. and a MultiReader constructed from other IndexReaders will
> never close them.
>
> -Hoss
>
>
> -----------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional co
: I use StandardAnalyzer.the records daily ranges from 5 crore to 6 crore. for
: every second i am updating my Index. i instantiate IndexSearcher object one
: time for all the searches. for an hour can i see the updated records in the
: indexstore by reinstantiating IndexSearcher object.but the pr
IndexReader indexSource4 =
>>>>>> IndexReader.open(indexDir4);
>>>>>>
>>>>>>
>>>>>>
cher(mergedReader);
>>>>>
>>>>>
>>>>> QueryParser parser =
>>>>> new QueryParser("contents" ,new
>>>>> St
yzer());
>>>>
>>>>
>>>> String searchQuery=
>>>> new
>>>> StringBuffer().append(inputNo).append(&quo
>>>
>>>
>>> Query callDetailquery =
>>> parser.parse(searchQuery);
>&g
>>
>> Query callDetailquery =
>> parser.parse(searchQuery);
>>
>> hits = is.search(callDetailquery);
>>
>>
>>
> hits = is.search(callDetailquery);
>
>
> it takes 300 MB of RAM for every search and it is very very slow is there
> any other way to control the Memory and to make search faster.i use
> SINGLETON to use the IndexSearc
ery search and it is very very slow is there
> any other way to control the Memory and to make search faster.i use
> SINGLETON to use the IndexSearcher as a one time used object for all the
> instances.
>
--
View this message in context:
http://www.nabble.com/Java-Heap-Space--Ou
callDetailquery);
it takes 300 MB of RAM for every search and it is very very slow is there
any other way to control the Memory and to make search faster.i use
SINGLETON to use the IndexSearcher as a one time used object for all the
instances.
--
View this message in context:
http://www.nabble.
30 matches
Mail list logo
