I am configuring solr locally for our apps and for some of our apps - we need to configure maxBooleanQueries in the solr configuration. Right now - we had set it to 8K ( as opposed to the default of 1K) . Our dataset document size is about 500K . We have about 6G of ram (totally) - so ignoring the app server + free space required for swap out - I would put the number around 4G for solr doc jvm instance.
Given these implications I am trying to figure out how far we can go with (how high ) maxBooleanQueries number since sometimes the boolean queries to be composed seems that long (huge list of terms to be OR-ed). * what are the space implications in terms of memory ( and then possibly disk usage ) * what are the time implications in terms of performance . One of the solutions that I had thought is to split the long boolean query into sub-queries and feeding in multiple queries. again - if we were take that route - what would the time / space considerations .
