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

viewing images is very slow #302

Closed
shoeper opened this issue Nov 9, 2014 · 5 comments
Closed

viewing images is very slow #302

shoeper opened this issue Nov 9, 2014 · 5 comments

Comments

@shoeper
Copy link
Collaborator

shoeper commented Nov 9, 2014

Viewing images in a folder containing many files is very slow.
I've got a folder with about 1250 images and viewing them in seahub is extremely slow (about 15 seconds wait time). Doing the same in folder with 5 images is very much faster (even with much bigger images).
When clicking on next the seaf-server uses 100% cpu for about 15 seconds. The servers CPU usage before clicking next is below 1 percent.
Edit: To be exact: chrome waits 15-16 seconds every time (so always the same time).
Getting the seafile overview takes 125ms.
Loading the large image folder takes 160ms (showing only first few files), every additional request to load more files names takes ~240ms.

Its a HP Proliant Micro Server G8 - Seafile perfoms very well on it but seahub is a bit slow from time to time. When uploading data I get 100MB/s (~1 Gbit/s - so faster than my computer can compute new blocks). Download speed is from 40-80MB/s constantly so viewing images shouldn't be any issue.
Maybe there is a problem in the way seafile is detecting which photo is being the next.

What about generating a list of files on viewing the first image and then just request the next one from the list via ajax (and maybe use auto preloading).

@freeplant
Copy link
Member

Do you view a folder containing images or view a single image file?

@shoeper
Copy link
Collaborator Author

shoeper commented Nov 10, 2014

I go into a folder containing many images. I view the first image and then I click next (and then again next and so on). According to chrome, chrome waits 15-16 seconds until the server has processed the request.

@shoeper
Copy link
Collaborator Author

shoeper commented Nov 10, 2014

I got what you mean: I view a single image file.
(But if this file is in a library with few files the request is answered fast. If this file is in a folder containing many files the request is answered very slow.)

@freeplant
Copy link
Member

This most likely to be caused by calculating "contributor" of a file (showing at the top of the file view). We will remove it and test the performance.

@shoeper
Copy link
Collaborator Author

shoeper commented Nov 10, 2014

ok thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants