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.

Sign up for GitHub

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

Jump to bottom

Mirador rendering performance is slow #31

Open

jamiefolsom opened this issue Sep 18, 2017 · 1 comment

Assignees

Member

jamiefolsom commented Sep 18, 2017 •

edited

Loading

Confirmed that this holds true:

With different manifests within mirador installed on Fauvel staging site from our IIIF server
With our manifest using the Project Mirador website demo install of the viewer
With other manifests, from other servers, on both our install of the client, and other clients.

Other information

There are at least three loading modes available (progressive, fade in, and tile); we should investigate to see which is preferable, and whether perceived performance is different.

TBD

To what extent network speed, proximity are issues
Whether server resources are issues
Whether our conversion process for pyramidal images is an issue
How mirador performs if/when images are bundled and/or served locally

jamiefolsom self-assigned this

Member Author

jamiefolsom commented Sep 18, 2017

As discussed on 9/18: for now, we're going to use either progressive or fade from black mode, and we'll keep this issue on our list.

jamiefolsom mentioned this issue

Mirador issues, questions, adjustments #25

Open

9 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment