Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating, modifying or deleting a collection type in Sirenia takes a really long time #6888

Closed
rjkati opened this issue Aug 14, 2024 · 3 comments · Fixed by #6925
Closed

Comments

@rjkati
Copy link

rjkati commented Aug 14, 2024

Descriptive summary

When I attempt to create, modify or delete a collection type in Sirenia, the action takes a really long time to complete.

Steps to reproduce the behavior in User Interface (UI)

  1. Log into your local build of Sirenia as an admin
  2. Navigate to Dashboard -> Collection Types
  3. Try to do an action on the Collection Types page

Note that each task completes as expected, it just takes forever to do so.

Actual behavior (include screenshots if available)

All testing occurred in my local build of Sirenia using Hyrax 5.0.1 in Google Chrome on Windows

  • Loading the collection types page: 35 seconds
  • Creating a new collection type: 7 minutes, 8 seconds
  • Modifying a collection type (I disabled Sharing on the Settings tab): 6 minutes, 17 seconds
  • Deleting a collection type: 1 minute, 43 seconds

For each task, Docker displays this message while running the task, in case it is helpful:
sirenia_collectiontypes

@eporter23
Copy link
Contributor

@rjkati - I tested some of this in our deployed Emory application also, so it's probably a little faster than the docker image, but still quite slow.
Loading the collection types page: 40 sec
Create a new Collection Type: 2 min 49 seconds
Modify the new Collection Type (added a badge color): 58 seconds
Delete the new Collection Type: 44 seconds

@dlpierce
Copy link
Contributor

I've noticed a similar pattern in the logs while running sirenia specs, so this likely has a large impact on rspec run time and performance in general.

@cjcolvar
Copy link
Member

I think I found the source of the problem and have a PR to resolve it: #6925

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants