: 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 on average but after some time
: this time goes up to about 30-40 seconds, altough the solr-outputted time
: stays between 0.8-1.3 seconds?
as Otis mentioned, that time is the raw processing of the request, not
counting any network IO between the client and the server, or any time
spent by the "ResponseWriter" formating the response. you can get more
accurate numbers about exctly how long the server spent doing all of these
things from the access log of your servlet container (which should be
recording the time only after every last byte is written back to the
client.
that said: there's really no reason for as big a descrepency as you are
describing particularly on updates where the ResposneWriter has almost
nothing to do (30-40 seconds per update?!?!?!)
I'm not very familiar with SolrJ, but are you by any chance using it in a
way that sends a commit after every update command? (commits can get
successifly longer as your index gets bigger.)
: Does this have anything to do with costly IO-activity that is accounted for
: in the SOLR output? If this is true, what tool do you recommend using to
: monitor IO-activity?
Which IO-activity are you talking about?
-Hoss
