Problematic setting lookups in generateNewCopy

Bug #1862068 reported by Jeff Davis on 2020-02-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

EG 3.3

We recently saw a single client send hundreds of simultaneous requests for the default copy status setting (cat.default_copy_status_normal; compare cat.default_copy_status_fast). The issue appears to be with the itemSvc.generateNewCopy function in the AngularJS volume/copy editor, which looks up the setting whenever a new acp object is generated. As currently written, these lookups are redundant (after the first one) and can cause drone saturation, so we should find another way of supplying the relevant values to new acp objects.

One solution would be to lookup and cache the cat.default_copy_status_normal and cat.default_copy_status_fast settings when the volume/copy editor is initially loaded. But the user may need to know the setting value for a library other than their current working location, so the client would need to be smart enough to cache the setting values for any possible org unit.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers