Steve Dondley
2021-Aug-25 18:51 UTC
[OT] Re: What kind of search response time are you setting with solr full text search?
On 2021-08-25 02:05 PM, Steve Dondley wrote:>> Try this in on the commandline of the Solr server: >> >> time curl >> "http://localhost:YYY/solr/dovecot/select?q=maynez&defType=edismax&qf=body+to+subject+cc+from" > > OK I had to modify the query path slightly to get it to work with my > core to: > > time curl > http://localhost:8983/solr/dondley/select?q=maynez&defType=edismax&qf=body+to+subjec:t+ccfrom >OK! found the issue. My command line mangled the URL when I edited the url. There is a stray ":" in the query string. So I am now seeing a ton of results and the following query time: real 0m0.118s user 0m0.003s sys 0m0.011s So this looks really good and fast. So I think we can say with confidence solr is doing its job. So why is roundcube/dovecot taking so long to show the results?
dovecot at ptld.com
2021-Aug-25 19:13 UTC
[OT] Re: What kind of search response time are you setting with solr full text search?
> So this looks really good and fast. So I think we can say with > confidence solr is doing its job. So why is roundcube/dovecot taking > so long to show the results?Random guess... Buffering? Whatever is sending to the browser isn't sending enough bytes to flush the buffer so the data is left in limbo until enough time goes by the buffer gets flushed anyways. Maybe a apache/nginx thing, php thing or browser thing. Remember its solr > dovecot > php > web server > browser. Tried other browsers?