Copied to clipboard

Flag this post as spam?

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

  • Gordon 21 posts 42 karma points
    May 19, 2014 @ 16:34

    Umbraco, caching, indexes and umbraco.config


    We have been using Umbraco for a few months now and I must admit, it's a great CMS to work with. I was hoping some of the smarter Umbraco peep's out there could provide me with some insight into some of the following questions relating to caching etc. I should mention the current installation is running on Azure websites accross 2 different instances (however they both point to the same file system)

    1. When a user publishes content in the admin, is this cached anywhere, and if so, where ( cache, file system, browser?)? Reason being, there have been instances where the client has published content, they can see the changes however it's not immediately visible from other connections, i.e. us.

    2. What is the purpose of the umbraco.config file. Is this where the live site reads it's content from? (We noticed it's a published version of all the content). And if so, is this cached at all? (if so, where, how and for how long?)

    3. If we delete the umbraco.config file, is this regenerated from the database? Or is this built using the Examine indexes?

    We have had some strange behaviour where the client publishes content, and then sometime later the changes are reverted. when they simply go in and republish it's fine again, however this is not desirable. If we had more on the info above it might provide some insight into this behaviour.

    Thanks and much appreciated for any assistance given!

    Lastly, is there documentation outlining this somewhere?



  • Sebastiaan Janssen 5039 posts 15427 karma points MVP admin hq
    May 19, 2014 @ 19:11
    Sebastiaan Janssen
    1. Make sure to set up load balancing properly if you want new content to be instantly visible everywhere:
    2. Yes and no. When your application pool starts, it gets the content from the easiest place it can get, if umbraco.config exists then it's super fast to read it from there, else it will read it from the database. From there on out the content cache lives in memory. It's cached in memory until you publish to it and then the changed parts are added/removed/updated (both in memory and to the file).
    3. Yep. Not using Examine indexes but the contentXml table.

    I think the problems you're running into are due to the load balancing not being set up properly like in the documentation.

    And a big for using Umbraco! :-)

Please Sign in or register to post replies

Write your reply to: