[Archivesspace_Users_Group] memory issues with reports in v2.3.0

[Yee, Karl]

On March 1st 2018 Kevin Clair Kevin.Clair at du.edu wrote:


Hello,



I was curious if anyone else on the list had noticed that reports (and possibly other background jobs) are consuming more memory in v2.3.0 than in previous versions of ArchivesSpace. We’ve noticed that reports that worked for us in 2.2.1 are throwing “GC overhead limit exceeded” errors since we upgraded.



We don’t use any of the default reports; every report we have in our instance is here: https://github.com/duspeccoll/archivesspace_reports. I’m sharing the link in case it’s a problem with our reports, and there are ways I could write them to be more efficient.



thanks!  -k

-------------- next part --------------

An HTML attachment was scrubbed...

URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180301/1c2fe62c/attachment.html>





Reply:



Hi Kevin



Yes, we’re having the same problem with our instance of ArchivesSpace ver 2.3 as well.  Even with the “canned” accession report. Like you, it’s throwing out “GC overhead limit exceeded” errors in the log and the whole reporting process just hangs.  The errors persists, even after we set ASPACE_JAVA_XMX="-Xmx2048m" within the archivesspace.sh script.

Has anyone found a solution?

Karl Yee
Computer Services Coordinator | Northeastern University Libraries | Library Technology Group
360 Huntington Ave. Boston, MA 02115 | (617) 373-4904 |   k.yee at northeastern.edu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180501/22aad98b/attachment.html>