Speed up media library

If you're able to, you can configure Azure to use CDN but that may require some changes within your Kentico configuration as well.

Hi, i want to come back to the question posted before by Ayoub. The problem is not to speed up media library for end user. But to speed up media library in order to allow to administrator to configure images faster more faster in media library.

As you can see on the image above, in my administration interface, when i have a lot of images in my mediaLibray it's take too long to load when i click on image. And it's take even too long when i try to swicth between folder. The screenshot below, is an example of dependencies that i have when i try to edit file in Media Libray. What i want it's a way to reduce that dependancies in other to speed up access and edition to files in Media library as this part is manage by Kentico.

Thank. Jeanne

Hi, i want to come back to the question posted before by Ayoub. The problem is not to speed up media library for end user. But to speed up media library in order to allow to administrator to configure images faster more faster in media library.

As you can see on the image above, in my administration interface, when i have a lot of images in my mediaLibray it's take too long to load when i click on image. And it's take even too long when i try to swicth between folder. The screenshot below, is an example of dependencies that i have when i try to edit file in Media Libray. What i want it's a way to reduce that dependancies in other to speed up access and edition to files in Media library as this part is manage by Kentico.

Thank. Jeanne

Kentico is going out to Azure to retrieve the images when you're in the Kentico UI and for the end user. So anything you can do on the Azure side to speed things up will Help in all places.

In this example, we have a folder with 111 images and for loading the page "Library_Edit_Files.aspx":

• it takes 23 seconds
• there are 537 dependencies and they are all done in sequence

This is approximatively 40ms per call which is not that long, but together its pretty intensive on the azure storage. The website is already a Premium P3 but the bottleneck seems to be about the network.