Daniel - regarding query time - yes, look at the response (assuming you are using XML responses) and look for "Qtime" in the top part of the response. That's the number of milliseconds it took to execute the query. This time does not include the network time (request to Solr + time to send the whole response back to the client).
US <--> Sweden.... nice.... ;) Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Daniel Andersson <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Tuesday, May 6, 2008 6:01:01 PM > Subject: Re: Help optimizing > > > On May 6, 2008, at 2:19 PM, Grant Ingersoll wrote: > > > On May 3, 2008, at 1:06 PM, Daniel Andersson wrote: > > > >> When performing a search, the results vary between 1.5 seconds up > >> to 60 seconds. > >> > > Is this pure Solr time or overall application time? I ask, b/c it > > is often the case that people are measuring application time and the > > problem lies in the application, so I just want to clarify. > > It's 1.5 to send the command to Solr, wait for it to search and get > the data back. > > The web server is located in the US and the Solr-machine is in Sweden > (don't ask), so I can see it taking a while to send data back and > forth, so getting the searches below 1.5s is not something I'm > expecting. I "just" want to get away from the >5s searches. > > Is there a way of getting Solr to output the total time spent on any > command? Just so I can eliminate some odd network problem/error. > > > > Also, have you done any profiling to see where the hotspots are? > > I have not. Not a Java person, so not sure how to do this. Is there > something in the Solr admin that will allow me to do this? Have looked > around and read what I could find in the Wiki, but didn't find > anything that looked like profiling. > > Cheers, > Daniel >
