Slow Responses for Media Object Edit Pages

[joncameron]

Description

Going through the edit steps for a media object can feel very slow, particularly when creating new items via the web interface, which is the common way to interact with item creation and editing for users. The requirement that each page is a step that must be navigated in a progression adds to this, especially since each page takes multiple seconds to return. This has been a common frustration for users adding new content.

Below are times reported by the network monitor in browser devtools in Firefox (avalon-dev) and Chrome (mco-staging) as a new item is created and "Save and continue" is selected to progress through the edit steps. Slower response times are expected on the development server, but the numbers from mco-staging show that this is across the board, and users in our production system wait for 17s+ for pages while creating a single item. Ideally this would be 1.5s or less for each page.

avalon-dev

Create new item (Manage Files): 7.84s
Resource Description: 3.92s
Structure: 10.78s
Access Control: 6.08s
Item Page: 1.92s

mco-staging

Create new item (Manage Files): 4.72s
Resource Description: 3.01s
Structure: 3.69s
Access Control: 4s
Item Page: 1.79s

Questions

• Is this just because of costly Fedora calls?
• Will Solr tuning help?
• Will other ongoing work (rethinking linked lists etc.) help with this, or are there other bottlenecks?

Done Looks Like

• Investigation/profiling of requests during processing and rendering of these pages