ned (there'll be a message in the log).
BTW, DocValues fields are strongly recommended for any field that gets
uninverted.
Best,
Erick
On Sun, Oct 16, 2016 at 10:28 PM, Dalton Gooding
wrote:
> Erick,
>
> I think you might have nailed it.
>
> After the three warming queries
uot;similar"
but slow. My _guess_
is that some innocent-seeming difference between the two is the issue.
Best,
Erick
On Sun, Oct 9, 2016 at 7:08 PM, Dalton Gooding
wrote:
> Erick,
>
> I have tried tuning the queries with some limited success. I still get
> drastic differences between th
e%29&start=0&rows=24'
real 0m1.436s
user 0m0.001s
sys 0m0.006s
"QTime":1387
>From what you suggested, changing the rows value from 20 to something
greater should add more documents to the cache. Injunction with tuning
the queries to remove the * wild c
rcher events get put into the cache.
So if you change the query even slighty my guess is that you'll see
response times very close to your
original ones of over a second.
Best,
Erick
On Thu, Oct 6, 2016 at 2:56 PM, Dalton Gooding
wrote:
> After setting a number of newSearcher and firstSearch
After setting a number of newSearcher and firstSearcher queries, I can see in
the console logs that the queries are run, but when I run the same query
against the new searcher (using CuRL), I get a slow response time for the first
run.
Config:
DataType_s:Product
