Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Tom Brian Stegmann 18 posts 133 karma points
    Jan 28, 2021 @ 12:28
    Tom Brian Stegmann

    Slow performance reg. Media items after Azure migration

    Hi friendly community, πŸ™‚

    After migrating an Umbraco solution (version 7.2.8) from a traditional web server setup to an Azure based setup, we are experiencing that accessing and navigating the Media items (from the backend) is suddenly extremely slow - and it is literally a drag to work with.

    It appears that it may have something to do with the way that Azure handles physical files – but a clear solution to the issue has not yet been found.

    A β€˜funny’ (well, not really) thing is that the speed is perfectly fine on the frontend – probably due to the extensive caching that Umbraco does. However, when accessing the Media files from the backend, the performance in terms of accessing the files and folders is very slow.

    It may, for instance, take between 8 – 12 seconds to navigate between folders, and the folders in question only contain a relatively small number of files; neither are those files particularly large.

    It has worked perfectly before with the previous setup (i.e. by traditional web server/hotel), but after migrating to the Azure setup, the performance of accessing and navigating Media elements has dropped significantly.

    Therefore – does anyone β€˜inhere’ have any experience with similar situations, and if so – did you find a solution to resolve the issue with super-slow Media file access?

    Thank you in advance, fellow Umbraco fanatics! 😊

    Best regards, Tom

  • Tom Brian Stegmann 18 posts 133 karma points
    Feb 10, 2021 @ 10:20
    Tom Brian Stegmann

    A solution has now been found - and for those who might be facing a similar situation in the future, I have added the 'fix' here...

    The problem turned out to be related to an abundant Media repository as well as the need for additional rebuilding and optimizing of the existing Examine indexes.

    After an extensive clean-up of the Media section, as well as subsequent index rebuilding, it seems to have resolved the issue. Furthermore, physical deletion of all cache files was also carried out - and the combination of these actions seems to have done the trick subsequent to the Azure migration. πŸ˜‰

Please Sign in or register to post replies

Write your reply to: