[Archivesspace_Users_Group] Memory problems

[Chelsea Lobdell]

Hi Megan,

Our installation of Archivesspace had very similar performance problems.
The logs were full of Java heap stack and out of memory errors. Solr logs
were will of Sever errors and the application started crashing. At first, a
restart would fix it but eventually, it would reach a slow down state very
quickly after a restart. Lyrasis sys admin pointed me to this ticket and
this plugin:

https://archivesspace.atlassian.net/browse/ANW-137

https://github.com/lyrasis/events-deduper

I recommend running the following query on your DB:

mysql> SELECT
  id,
  archival_object_id,
  event_id,
  role_id,
  COUNT(*) as duplicates
FROM `event_link_rlshp`
GROUP BY archival_object_id, event_id, role_id
HAVING duplicates > 1
ORDER BY duplicates DESC;

If you have a high number of duplicates, I would try the plugin.

- Chelsea


*---------------*
*Chelsea Lobdell*
*Library Web Developer/ Swarthmore College*
*clobdel1 at swarthmore.edu <clobdel1 at swarthmore.edu> / (610)690-6818*

On Wed, Aug 2, 2017 at 1:23 PM, Mummey, Megan <megan.mummey at uky.edu> wrote:

> Hi all,
>
>
>
> UK’s locally installed instance of ArchivesSpace has performance issues
> every couple of months, slowing down until eventually the application is
> fails. The fix is a full restart. Our programmer has indicated the failure
> is caused by “garbage collecting”. Previously we’ve added RAM to our VM.
> We’re interested in finding out how other institutions with a similar sized
> SOLR index are running ArchivesSpace. And if they have/had similar problems.
>
>
>
> Information on our system below:
>
>
>
> ·        ArchivesSpace directory is about 26 GB.  This includes two
> copies of the Solr index (the live version and a backup, at about 3 GB
> each) and 19 GB of log files.  This is housed on a network share with
> terabytes of free space.
>
> ·        The ArchivesSpace database is housed on the libwwwapps07 VM.
> The ibdata1 file for MySQL (used for all databases on the VM but primarily
> used by ArchivesSpace) is about 2.4 GB.  The VM has about 35 GB free.
>
> ·        ArchivesSpace is configured with the following settings:
>
>
>
>   + ASPACE_JAVA_XMX="-Xmx6144m"
>
>   + AppConfig[:indexer_thread_count] = 2
>
>
>
> ·        MySQL is configured with the following setting:
>
>
>
> + innodb_buffer_pool_size= 1600000000
>
>
>
> ·        VM has approximately 8 GB of RAM. The value of ASPACE_JAVA_XMX
> is lower than this to allow memory use by other processes, including MySQL
> (as listed above) and the web server.
>
>
>
> Thanks,
>
>
>
> Megan Mummey
>
> Collections Management Archivist
>
> Special Collections Research Center
>
> University of Kentucky Libraries
>
> Margaret I. King Library
>
> Lexington, KY  40506-0039
>
> megan.mummey at uky.edu <Megan.mummey at uky.edu>|859.257.6942
> <(859)%20257-6942>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170802/74764685/attachment.html>