: Index has 41 000 000 documents and 9 GB size. For query like: : 1) : *q=Jarecki+Jan*&fq=sex:M&fq=confirmed:1&fq=show_search:3&fl=user_id&start=0&rows=10&wt=json&version=2.2 : : server reaches avarage *90 query/s* on 4 theards and is very small for me. : : For query with filer on filed city: : 2) ex. : fl=user_id&indent=on&start=0&q=Tarkowski+Bartłomiej&wt=json&*fq=city:Kwidzyn*&fq=sex:M&fq=confirmed:1&fq=show_search:3&version=2.2&rows=10 : : server reaches 800 query/s. : : Do you have any advice to speed the search for first query? Is this speed is : the norm?
"norm" is hard to define, but one key element you left out is how many docs are (typically) matched by requests of type #1 vs type #2. and how good a job your "city" filters do in partitioning the total number of documents. I suspect that your city filters are heavily reused (ie: good cache hit rates) and do a really good job of cutting down the number of matching docs -- (ie: num docs matching fq=sex:M&fq=confirmed:1&fq=show_search:3 is probably significantly higher then num docs matching fq=sex:M&fq=confirmed:1&fq=show_search:3&fq=city:Kwidzyn ). In which case it makes sense that type#1 queries would take a lot longer on average -- there are a lot more docs to consider when evaluating the "q" to find matches. -Hoss
