Thanks a lot guys. I really appreciate your response on my query. I'll
create multiple threads and checkout that how much I can rate can be
increased per thread.
Regards,
Sandeep
On Tue, Feb 23, 2016 at 4:19 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> Your profiler breakdown is
Your profiler breakdown is exactly what I'd expect: processing the
fields is the heaviest part of indexing.
Except, it doesn't have any merges? Did you run it for long enough?
Note that by default Lucene runs merges in a background thread
(ConcurrentMergeScheduler). If you really must be single
.de
eMail: u...@thetaphi.de
> -Original Message-
> From: sandeep das [mailto:yarnhad...@gmail.com]
> Sent: Tuesday, February 23, 2016 8:30 AM
> To: java-user@lucene.apache.org
> Subject: Re: Profiling lucene 5.2.0 based tool
>
> Hi Rob,
>
> The statistics which I ha
Hi Rob,
The statistics which I had shared were provided using one thread for
indexing. I wish to use only 1 thread and want to process maximum
10MBps(Mega Bytes per second) of data rate. I believe with single thread it
should be achievable.
Regards,
Sandeep
On Tue, Feb 23, 2016 at 12:50 PM, Rob
Hi Sandeep,
How many threads do you use to do the indexing? The benchmarks of Lucene
are done on >20 threads IIRC.
-Rob
On Tue, Feb 23, 2016 at 8:01 AM, sandeep das wrote:
> Hi,
>
> I've implemented a tool using lucene-5.2.0 to index my CSV files. The tool
> is reading data from CSV files(resi
