[Yale ArchivesSpace] FW: ArchivesSpace Update from Library IT

[Caldera, Mary]

Resending  Melissa's update as it does not seem to have gone through. -- mary

From: Wisner, Melissa
Sent: Thursday, June 18, 2015 5:26 PM
To: yulaspace at mailman.yale.edu<mailto:yulaspace at mailman.yale.edu>
Subject: ArchivesSpace Update from Library IT

Hello Everyone,

Library IT would like to provide an update on the work being performed to resolve system performance issues with production ArchivesSpace.

Here is a quick recap of our remediation:

*         A monitoring tool, New Relic, is configured to report system activity and breakdown performance from our test and dev instance of AS

*         Our test and dev instances have copies of production data so testing environments are comprehensive

*         Documentation is in progress to list the configuration settings of each instance to identify any inconsistencies that might be contributing to performance variations

*         Yale Network ruled out as a contributing factor to poor system performance

*         CPUs and Memory added to all AS servers

*         MYSQL update to 5.6, Java downgrade to version 7

*         Library IT is consulting with Lyrasis, a registered service provider of ArchivesSpace

*         Library IT is requesting the paid services of HM, the developers of AS and the developers of YUL's custom AS plugins

Steps in progress:

*         Review of the slow query logging data to identify SQL that could be optimized

*         An examination of the JRuby error messages in the application logs

*         Finalizing a "vanilla" version of AS (no custom YUL Plugins) with our data for additional comparison testing

Reminders:

*         It is OK to use production AS as much as you need to. System performance has improved, but still may be sub-standard depending on the activity

*         Continue to report any issues to libraryit.entsys at yale.edu<mailto:libraryit.entsys at yale.edu>

YUL is one of the largest sites using AS in production. Several of our peers are in earlier phases of implementation, although we are not without company. One example is BYU. They are not using the custom plugins YUL is, but they are indicating some system performance standards are not being met, such as length of time to save a record. Our goal is to meet the requirements our special collection colleagues need to perform at their best. The complete solution may not arrive as quickly as we desire, but this is a top priority for Library IT. I think it is important to note that while there is a sense of urgency to resolve the current situation, this issue illuminates the need for expertise and systems coordination for the lifespan of ArchivesSpace at YUL.

Thank you for your patience,
Melissa Wisner
Library IT

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.yale.edu/pipermail/yulaspace/attachments/20150619/83af3546/attachment.html