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

Metadata editor is slow to respond #4196

Closed
matthias-ronge opened this issue Feb 18, 2021 · 5 comments
Closed

Metadata editor is slow to respond #4196

matthias-ronge opened this issue Feb 18, 2021 · 5 comments
Assignees

Comments

@matthias-ronge
Copy link
Collaborator

For a process with a large number of images, the metadata editor is sluggish. A yellow bar appears in the browser:

A web page is slowing down

Mark a series of 16 pictures with the mouse (click on the first picture, Shift + click on the last picture) the loading key symbol rotates for 4 minutes. It takes 3 minutes to move the images with the mouse.

Long

Goal: The speed of interaction must be improved.

@solth
Copy link
Member

solth commented Feb 24, 2021

I just tried this with a process with over 400 pictures.
These are the times I observed in my browser (Firefox) with > 200 open tabs and several other ressource hungry programs like IntelliJ or ElasticSearch running in the background:

  • opening the process in the metadata editor: 5 seconds
  • creating a new structure element: 3 seconds
  • selecting > 50 thumbnails in the gallery: 2 seconds
  • moving the selected thumbnails to the new strucutre element via drag'n'drop: ~ 15 seconds

(My browser did not display any warning that the current tab would slow things down.)
So moving a larger stack of images at once definitely takes some time, but is far away from the times you reported. All tested on a Kitodo.Production 3 installation on a server with fairly moderate hardware specifications.

Could it be you were testing locally on your development machine and your system load was too high? Perhaps the debugger was running and many breakpoints decreased performance?

@matthias-ronge
Copy link
Collaborator Author

matthias-ronge commented Mar 16, 2021

No, we tested on a server installation. As far as I can tell so far, two effects played a role:

  1. the web browser was running on the same PC on which the video conference via MS Teams was running at the same time. Both require considerable resources. Starting the web browser in another machine via RDP makes the warning bar stay away. (Still, the fact that the browser needs so much resources is a lot.)
  2. The process had well over 1000 images. Unfortunately, I have meanwhile deleted the process and no longer know how many there were. I think 1600 pictures. I was told: This is not unusual, and it has to be editable nonetheless. (I also know of processes with over 2000 images in Production 2, although I advise against it. It's also slower then, but it shouldn't be that slow. )
    Sorry, I should have written that into the issue right away.

@Kathrin-Huber
Copy link
Contributor

@matthias-ronge can you confirm, that this is fixed with the newest release?

@matthias-ronge matthias-ronge self-assigned this Jun 3, 2022
@solth solth removed the 3.x label Jul 7, 2022
@matthias-ronge
Copy link
Collaborator Author

I didn’t see this message again with newer versions.

@matthias-ronge matthias-ronge closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants