sage
> > From: Geert-Jan Brits <[EMAIL PROTECTED]>
> > To: solr-user@lucene.apache.org
> > Sent: Thursday, January 17, 2008 6:10:56 AM
> > Subject: Re: batch indexing takes more time than shown on SOLR output
> -->
> > something to do with IO?
> >
>
ext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
> - Original Message
> From: Geert-Jan Brits <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Thursday, January 17, 2008 6:10:56 AM
> Subject: Re: batch indexing takes more time than shown on SOLR ou
IL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Thursday, January 17, 2008 6:10:56 AM
Subject: Re: batch indexing takes more time than shown on SOLR output -->
something to do with IO?
No Solr-commit is sent until the end.
Since client and server on this moment are on the same machine network
No Solr-commit is sent until the end.
Since client and server on this moment are on the same machine network IO
should be small as well I think. Also as you mentioned the response is very
small so it can't be that either.
As to what IO-activity I was thinking about: I was merely guessing here, but
: INFO: {add=[10485, 10488, 10489, 10490, 10491, 10495, 10497, 10498, ...(42
: more)
: ]} 0 875
:
: However, when timing this instruction on the client-side (I use SOlrJ -->
: req.process(server)) I get totally different numbers (in the beginning the
: client-side measured time is about 2 seconds
logs.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Britske <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Monday, January 14, 2008 10:56:24 AM
Subject: batch indexing takes more time than shown on SOLR output -->
something
I have a batch program which inserts items in a solr/lucene index.
all is going fine and I get update messages in the console like:
14-jan-2008 16:40:52 org.apache.solr.update.processor.LogUpdateProcessor
finish
INFO: {add=[10485, 10488, 10489, 10490, 10491, 10495, 10497, 10498, ...(42
more)
]}
