Hi Uwe, sorting should be well prepared. First rough check is fieldCache. You can see it with SolrAdmin Stats. The "insanity_count" there should be 0 (zero). Only sort on fields which are prepared for sorting and make sense to be sorted.
Do only faceting on fields which make sense. I've seen systems with faceting on "id", this is a no-go and doesn't make sense. The system pulls a lot of data from the index into memory which can lead to OOME. How to figure out what is killing your system? There is no general rule but what you can do is: - Start your test-system and make sure noone else is using it. - Start a monitor for your JVM running SOLR (e.g. jvisualvm). - use your search frontend and do searches, sorting, faceting of any combination possible and watch your heap memory if it has big jumps in memory heap. - Analyze your search log files and look for searches which have a very high Qtime. Repeat the searches with high Qtime and see if you get "insanity_counts" or heap memory jumps in JVM. Regards Bernd Am 06.12.2012 23:27, schrieb uwe72: > Hi there, > > since i use a lot sorting and faceting i am getting very often an > OutOfMemoryError. > > I have arround > 6 million documents, > index size arround 18GB and using > tomcat with 1.8 GB max heap size. > > What can i do? What heap size is recommended in our case? > > Can i do other things in order to prevent OutOfMemoryError while using a lot > of facets? > > Urgent, please help. > > Thanks, > Uwe > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/OutOfMemoryError-While-Faceting-Query-tp4024947.html > Sent from the Solr - User mailing list archive at Nabble.com. >
