Title: Message Title
|
|
|
|
|
|
Discovery SolrLogger changes in DSpace 3.0 cause entire Item Bitstreams to be copied into Strings (which then get copied into byte arrays and finally copied into response output to Solr) This is inefficient and causes Indexing to bound to JVM Memory footprint.
SolrLogger originally passed the Bitstream. retireve retrieve () InputStream to Solr for indexing, Solr treats InputStreams differently than Strings and holds them until needed in the Http Post request.
The following change assures a consistent memory footprint for Solr Indexing.
https://github.com/DSpace/DSpace/pull/515
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
