I have plenty of images path of my Rad Editor set to a folder with many sub folders. Each of those sub folders has dozens of images in it. On the production server, it takes almost a minute just for the Image Manager dialog to open and show the sub folders.and also taking long time on pagination as well filtration
I made changes in web.config as advised like below
<compilation debug="false" strict="false" explicit="true">
Still, I could not find any difference . Please advise , is there any way to improve the performance of the image manager.
I made changes in web.config as advised like below
<compilation debug="false" strict="false" explicit="true">
Still, I could not find any difference . Please advise , is there any way to improve the performance of the image manager.
1 Answer, 1 is accepted
0
Hi John,
The loading time of FileExplorer (the control used for listing files and folders in the Editor's ImageManager) depends on the count of the subfolders inside the currently loaded folder. The current behavior of RadFileExplorer is to call ResolveRootDirectoryAsTree method for each subfolder of the one that is currently requested to check if they have content, so decreasing this count should improve the loading time.
Another possible option you could try is to remove the TreeView from the visible controls of FileExplorer in case this would be acceptable for your scenario. Furthermore, if you choose this option you can optimize the performance even more by enabling VirtualScrolling for the RadGrid component in RadFileExplorer like explained in the following KB:
Setup virtual scrolling in the RadGrid embedded in RadFileExplorer
On a site note, we have planned improvements for the control in scenarios with large amount of files / folders, but unfortunately, I am not able to provide firm estimate for when it will be implemented (if possible).
Hope this information will be helpful for you.
Regards,
Vessy
Telerik
The loading time of FileExplorer (the control used for listing files and folders in the Editor's ImageManager) depends on the count of the subfolders inside the currently loaded folder. The current behavior of RadFileExplorer is to call ResolveRootDirectoryAsTree method for each subfolder of the one that is currently requested to check if they have content, so decreasing this count should improve the loading time.
Another possible option you could try is to remove the TreeView from the visible controls of FileExplorer in case this would be acceptable for your scenario. Furthermore, if you choose this option you can optimize the performance even more by enabling VirtualScrolling for the RadGrid component in RadFileExplorer like explained in the following KB:
Setup virtual scrolling in the RadGrid embedded in RadFileExplorer
On a site note, we have planned improvements for the control in scenarios with large amount of files / folders, but unfortunately, I am not able to provide firm estimate for when it will be implemented (if possible).
Hope this information will be helpful for you.
Regards,
Vessy
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.