Sorting on field X will build an array of the size of maxDoc. The data type equals the one used by the field you're sorting on. Also, if you have a very high amount of deletes per update it might be a good idea to optimize as well since it reduces maxDoc to the number of documents that actually can be found.
> We do have sorting but not faceting. OK so I guess there is no 'hard and > fast rule' as such so I will play with it and see. > > Thanks for the help > > On Wed, Jan 19, 2011 at 11:48 PM, Markus Jelsma > > <markus.jel...@openindex.io>wrote: > > You only need so much for Solr so it can do its thing. Faceting can take > > quite > > some memory on a large index but sorting can be a really big RAM > > consumer. > > > > As Erick pointed out, inspect and tune the cache settings and adjust RAM > > allocated to the JVM if required. Using tools like JConsole you can > > monitor various things via JMX including RAM consumption. > > > > > Hi, > > > > > > I know this is a subjective topic but from what I have read it seems > > > more RAM should be spared for OS caching and much less for SOLR/Tomcat > > > even on > > > > a > > > > > dedicated SOLR server. > > > > > > Can someone give me an idea about the theoretically ideal proportion > > > b/w them for a dedicated Windows server with 32GB RAM? Also the index > > > is updated every hour.
