We should consider adding another parameter "RealTime" in the log. That would really help all of us trying to figure out how much time a query is taking.
On Tue, Jun 4, 2013 at 5:14 PM, Otis Gospodnetic <otis.gospodne...@gmail.com > wrote: > Right. The main takeway is that QTime is not exactly what user sees. > What users sees is always > QTime. To see what end users experience > one needs RUM (and I don't mean the tasty kind, but > http://en.wikipedia.org/wiki/Real_user_monitoring . > > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Tue, Jun 4, 2013 at 11:54 AM, Walter Underwood <wun...@wunderwood.org> > wrote: > > On Jun 4, 2013, at 8:28 AM, Shawn Heisey wrote: > > > >> On 6/4/2013 8:45 AM, O'Regan, Mike wrote: > >>> Can't a GC also kick in before the timer starts, resulting a short > QTime but a long time from the point of view of the client? Believe I have > seen that phenomenon in action. > >> > >> You are correct. I don't know why I didn't think of that. > >> > >> Thanks, > >> Shawn > > > > > > If I remember correctly, QTime does not include the time to fetch the > field data after the query is evaluated and scored. It also does not > include the time to send the data. > > > > wunder > > > > > > > > > -- Bill Bell billnb...@gmail.com cell 720-256-8076
