tor (e.g. Java 7 G1 Collector or
> >>>> Java 6
> CMS
> >> Collector). Other garbage collectors may do GCs in a single thread
> ("stop-the-
> >> world").
> >>>> Uwe
> >>>> -
> >>>> U
ollector (e.g. Java 7 G1 Collector or Java
>>>> 6 CMS
>> Collector). Other garbage collectors may do GCs in a single thread
>> ("stop-the-
>> world").
>>>> Uwe
>>>> -
>>>> Uwe Schindl
gt;> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>> -Original Message-
> >>> From: Igor Shalyminov [mailto:ishalymi...@yandex-team.ru]
> >>> Sent: Saturday, November 23, 2013 4:46 PM
> >>> To: java-user@luce
ported" setup :-) Lucene has no problem with that setup and can index.
>> Be sure:
>> >> - Don't give too much heap to your indexing app. Larger heaps create
>> much more GC load.
>> >> - Use a suitable Garbage collector (e.g. Java 7 G1 Collector or Java
gt;> -
> >> Uwe Schindler
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>> -Original Message-
> >>> From: Igor Shalyminov [mailto:ishalymi...@yandex-team.ru]
> &g
>> Uwe
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>> -Original Message-
>>> From: Igor Shalyminov [mailto:ishalymi...@yandex-team.ru]
>>> Sent:
riginal Message-
From: Igor Shalyminov [mailto:ishalymi...@yandex-team.ru]
Sent: Saturday, November 23, 2013 4:46 PM
To: java-user@lucene.apache.org
Subject: Re: Lucene multithreaded indexing problems
So we return to the initially described setup: multiple parallel workers, each
making "p
Maybe you should turn on Garbage Collection logging to confirm that you
are running into some kind of memory problem. (start JVM with -verbose:gc)
If the GC is running very often as soon as your indexing process slows
down, i would suggest you to create a heapdump and check what the memory
is us
e
eMail: u...@thetaphi.de
> -Original Message-
> From: Igor Shalyminov [mailto:ishalymi...@yandex-team.ru]
> Sent: Saturday, November 23, 2013 4:46 PM
> To: java-user@lucene.apache.org
> Subject: Re: Lucene multithreaded indexing problems
>
> So we return to the initially de
wrong, too.
>>> Uwe
>>>
>>> -
>>> Uwe Schindler
>>> H.-H.-Meier-Allee 63, D-28213 Bremen
>>> http://www.thetaphi.de
>>> eMail: u...@thetaphi.de
>>>> -Original Message-
>>>> From: Igor Shalym
hope you will not do), things
>will go wrong, too.
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>> -Original Message-
>>> From: Igor Shalym
r Shalyminov [mailto:ishalymi...@yandex-team.ru]
>> Sent: Thursday, November 21, 2013 4:45 PM
>> To: java-user@lucene.apache.org
>> Subject: Lucene multithreaded indexing problems
>>
>> Hello!
>>
>> I tried to perform indexing multithreadedly, with a F
Hello!
I tried to perform indexing multithreadedly, with a FixedThreadPool of Callable
workers.
The main operation - parsing a single document and addDocument() to the index -
is done by a single worker.
After parsing a document, a lot (really a lot) of Strings appears, and at the
end of the wo
.ru]
> Sent: Thursday, November 21, 2013 4:45 PM
> To: java-user@lucene.apache.org
> Subject: Lucene multithreaded indexing problems
>
> Hello!
>
> I tried to perform indexing multithreadedly, with a FixedThreadPool of
> Callable workers.
> The main operation - parsing a si
14 matches
Mail list logo
