I'm really at dead point.
Mine indeks is 5,6GM and about 8mln documments.
Field i'm using for filter is simple as hell.
Can it be that other fields affect my search if i only do filter query?
solr/puls-objects-prod/select?q=*%3A*&fq=class_name:License
mine results:
831
*:*
class_name:
On Sat, May 31, 2014 at 8:47 AM, mizayah wrote:
> i show you my full query
>
> it's rly simple one
> q=*:* and fq=class_name:CdnFile
>
> debug q shows that process of q takes so long.
> single filter is critical here.
400ms is too long... something is strange.
One possibility is that the part of
i show you my full query
it's rly simple one
q=*:* and fq=class_name:CdnFile
debug q shows that process of q takes so long.
single filter is critical here.
And cache is ot an option here. It work well but i need to know why such
sipmple filter can takes so long.
class_name:CdnFile
421.0
Add the debugQuery=true parameter and look at the "timing" section to see
which search component is consuming the time. Are you using faceting or
highlighting?
7 million documents is actually a fairly small index.
-- Jack Krupansky
-Original Message-
From: mizayah
Sent: Wednesday, M
Could you please share the solrconfigs and schema here for more debugging
the issue as well as you could also try by adding the extra parameter
(&debugQuery=true) to your request params. Then you can view the
parsed_query, the actual query parsed by solr.
With Regards
Aman Tandon
On Thu, May 1
the first time you use any fq clause, it's evaluated pretty much as
though you'd just ANDed it in to the main clause. It's only if you use
the fq clause again that the query can take advantage of the caching.
But one query does not a pattern make. Is this right after you've
started the server? Or
