Let's see the query. If you do anything with dates using NOW (without rounding), the queries are actually not the same since NOW resolves itself to the epoch and will change every millisecond.
Best, Erick On Thu, Mar 10, 2016 at 12:18 AM, Murali TV <murali...@gmail.com> wrote: > Hi, > > I have a query that takes about 5secs to complete. The result count is > about 250 million, and row size is about 25. > The problem is that this query result is not getting loaded to the query > cache, so it takes ~5secs every time its issued. I also confirmed this by > looking at the cache stats page in the admin console. The query cache size > and inserts counts don't increase. The cache lookup counts increment but > cache hits count stays the same for every instance of the query. > > If I modify the query such that the query returns in about 4.5 secs, this > second query does get cached and subsequent calls return in milliseconds. > The cache stats page shows the cache size and insert counts increase by 1 > for the first query, and cache hits count increases for subsequent queries. > > What's the reason for the first query not getting cached when the request > takes >5 secs? Is there any configuration around this? > > Thanks. > Murali
