Mosaic Dataset containing 1500+ Images, need help with functional

[sophered]

Hello!

I am looking for some guidance on creating a mosaic dataset to be used within an application in Portal! The goal of the current project that I am working on is to display 1500+ images within a visually appealing application that allows users to search for certain attributes and view the images based on that. So far, I have been able to create a mosaic dataset with ~10 images in it and publish it as an referenced imagery layer that is used in my application (Web AppBuilder since nothing else seems compatible with Imagery Layers in our current portal version). 

The issue that I am currently dealing with is how SLOW the application is for only 10 images. I am worried that if we get up to our goal of 1500 images within that mosaic dataset, the application itself will be impossible to use because of slow loading times. I am using a pretty simplistic workflow for the mosaic dataset: add images to mosaic dataset, publish as imagery layer. Is there any settings that I can apply or any steps that I can implement to make this layer better to use within an application?

[lah]

We have a similar use case where we are publishing thousands of orthomosaics in a MDS to portal (also disappointed with the lack of image service support in Enterprise). I've learned it's really more about how and where your imagery is stored that's going to make the biggest difference. Ours our stored as COG files in S3, so the biggest lag time is the server talking to the bucket. There's also caching and things you can put in place; I've found these resources to be the most helpful:

Imagery: Data Management Patterns and Recommendations

Imagery formats and performance