[
https://jira.duraspace.org/browse/DS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25842#comment-25842
]
DSpace @ Lyncode commented on DS-1205:
--------------------------------------
Richard,
i was meditating on this issue. EhCache configuration allows one to configure
it as a persistent cache.
<cache name="copyCache"
maxEntriesLocalHeap="10"
eternal="false"
timeToIdleSeconds="5"
timeToLiveSeconds="10"
overflowToDisk="false"
copyOnRead="true"
copyOnWrite="true">
<copyStrategy class="com.company.ehcache.MyCopyStrategy"/>
</cache>
Avoiding the OutOfMemory/NullPointer issue. I've noticed that DSpace devel team
agrees on improving the current DSpace ORM implementation, as so, this issue
would be solved in the future (at least i believe so). Anyway, it's dangerous
to have the actual behavior, mainly because there are many new and old
developments that uses this API (obviously) and DSpace team must check (or
believe) that they are aware of it.
Finally, i'm not able to answer the following question:
- What are the minimum memory requirements for Dspace installation?
There is some documentation about it [1, 2], but it seems like there is no
control over DSpace memory usage, my experience says that DSpace is a big
memory consumer.
[1]
http://dspace.2283337.n4.nabble.com/MINIMUM-HARDWARE-REQUIREMENTS-FOR-DSPACE-INSTALLATION-td3282776.html
[2]
https://wiki.duraspace.org/display/DSPACE/EndUserFaq#EndUserFaq-WhatsortofhardwaredoesDSpacerequire%3FWhataboutsizingtheserver%3FHowmuchdiskspacedoIneed%3F
> DSpace org.dspace.core.Context caching problem
> ----------------------------------------------
>
> Key: DS-1205
> URL: https://jira.duraspace.org/browse/DS-1205
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.8.2
> Reporter: DSpace @ Lyncode
> Priority: Blocker
> Labels: Core
> Fix For: 3.0
>
>
> bin/dspace script is crashing with OutOfMemory problems related with the
> org.dspace.core.Context HashMap.
> Proof: https://github.com/lyncode/DSpace/issues/5
> I think this is a critical problem, mainly because it does not make sense
> (for me) to have crashing applications because of caching mechanism memory
> overusage. As good practices for implementing caches, this cache mechanism
> could be aware of it's memory usage threshold, if reached, it could start
> discarding old and unused objects in it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
