[Archivesspace_Users_Group] Problems working with archival object with large number of direct children

[Ryan Edwards]

Hello Sally,

We’ve also noticed that it can take a while (2-3 minutes) to load one of our largest resources, even after we increased the physical RAM on our server.

-Ryan

Ryan Edwards
Digital Access and Systems Librarian
Getty Research Institute

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Sally Vermaaten
Sent: Tuesday, November 15, 2016 11:38 AM
To: archivesspace at googlegroups.com; Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children

Hi everyone,

We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:
·  it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy
·  it takes a couple of minutes to open any archival object in the series in edit mode and
·  it takes a couple of minutes to save changes to any archival object within the series
Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?

The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.

We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?

Thanks,
Weatherly and Sally

--
Sally Vermaaten
Project Manager, Archival Systems
New York University Libraries
1-212-992-6259
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/255cb23a/attachment.html>