Hi Shawn, We have already switched the request method to POST. I am going to try the term query parser soon. I will post the performance difference against the IN syntax here later.
Thanks! 2015-11-20 15:23 GMT-08:00 Shawn Heisey <apa...@elyograg.org>: > On 11/20/2015 4:09 PM, jichi wrote: > > Thanks for the quick replies, Alex and Jack! > > > >> definitely can improve on the ORing the ids with > > Going to try that! But I guess it would still hit the > maxBooleanClauses=1024 > > threshold. > > The terms query parser does not have a limit like boolean queries do. > This query parser was added in version 4.10, so be aware of that. > Querying for a large number of terms with the terms query parser will > scale a lot better than a boolean query -- better performance. > > The number of terms you query will affect the size of the query text. > The query size is constrained by either the max HTTP header size if the > request is a GET, or the max form size if it's a POST. The max HTTP > header size is configurable in the servlet container (jetty, tomcat, > etc) and I would not recommend going over about 32K with it. The max > form size is configurable in solrconfig.xml with the > formdataUploadLimitInKB attribute on the requestParsers element. That > attribute defaults to 2048, which yields a default size of 2MB. > Switching your queries to POST requests is advisable. > > Thanks, > Shawn > > -- jichi
