Hi! When I write from our database to a HttpSolrServer, (using a LinkedBlockingQueue to write just one document at a time), I run into memory problems (due to various constraints, I have to remain on a 32-bit system, so I can use at most 2 GB RAM).
If I use an EmbeddedSolrServer (to write locally), I have no such problems. Just now, I tried out ConcurrentUpdateSolrServer (with a queue size of 1, but 3 threads to be safe), and that worked out fine too. I played around with various GC options and monitored memory with jconsole and jmap, but only found out that there's lots of byte arrays, SolrInputFields and Strings hanging around. Since ConcurrentUpdateSolrServer works, I'm happy, but I was wondering if people were aware of the memory issue around HttpSolrServer. Regards, Britta Rogowski __________________________________ Britta Rogoswki Senior Developer Wolters Kluwer Deutschland Online Product Development Feldstiege 100 48161 M?nster Tel +49 (2533) 9300-251 Fax brogow...@wolterskluwer.de Wolters Kluwer Deutschland GmbH | Feldstiege 100 | D-48161 M?nster | HRB 58843 Amtsgericht K?ln | Gesch?ftsf?hrer: Dr. Ulrich Hermann (Vorsitz), Michael Gloss, Christian Lindemann, Frank Schellmann | USt.-ID.Nr. DE188836808
