[ 
https://jira.duraspace.org/browse/DS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bram Luyten (@mire) updated DS-1553:
------------------------------------

    Description: 
When using Tomcat 7.0.29, heap space shoots up to over 600MB when starting up 
DSpace, only deploying the XMLUI exploded war. Even without SOLR. 

Using Tomcat 7.0.40, this is no longer the case and just uses 50MB of heap. 

Right now, I'm not sure whether this is just a local configuration problem, or 
whether there's a serious reason to put a warning in the docs to ensure that 
people don't use 7.0.29.

Would be great if anybody is able to reproduce/confirm this excessive memory 
usage on tomcat 7.0.29.

Java opts for 7.0.29 -Xms1024m -Xmx1024m (won't even run without declaring more 
heap space).

  was:
When using Tomcat 7.0.29, heap space shoots up to over 600MB when starting up 
DSpace, only deploying the XMLUI exploded war. Even without SOLR. 

Using Tomcat 7.0.40, this is no longer the case and just uses 50MB of heap. 

Right now, I'm not sure whether this is just a local configuration problem, or 
whether there's a serious reason to put a warning in the docs to ensure that 
people don't use 7.0.29.

Would be great if anybody is able to reproduce/confirm this excessive memory 
usage on tomcat 7.0.29.

    
> Huge heap on Tomcat 7.0.29
> --------------------------
>
>                 Key: DS-1553
>                 URL: https://jira.duraspace.org/browse/DS-1553
>             Project: DSpace
>          Issue Type: Documentation
>            Reporter: Bram Luyten (@mire)
>
> When using Tomcat 7.0.29, heap space shoots up to over 600MB when starting up 
> DSpace, only deploying the XMLUI exploded war. Even without SOLR. 
> Using Tomcat 7.0.40, this is no longer the case and just uses 50MB of heap. 
> Right now, I'm not sure whether this is just a local configuration problem, 
> or whether there's a serious reason to put a warning in the docs to ensure 
> that people don't use 7.0.29.
> Would be great if anybody is able to reproduce/confirm this excessive memory 
> usage on tomcat 7.0.29.
> Java opts for 7.0.29 -Xms1024m -Xmx1024m (won't even run without declaring 
> more heap space).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to