Skip to main content

Toolkit - Cache Invalidation

This post if part of a series about the File System Toolkit - a custom content delivery API for SDL Tridion.

In previous post, I explained the use of a Cache Factory. This post describes a very simple cache invalidation mechanism the Toolkit uses in order to make sure it does not serve stale values (for a long time).

Given the nature of the Toolkit storage, i.e. files on a file-system, it is very easy to check when they were last published. By simply looking at the JSON model file last modified attribute, one can see the very moment that model was created/updated. This is the last publish time-stamp as well.

When a CacheElement is placed in cache, it is also given a last-check timestamp, which initially is set to now. This last-check will be greater than the JSON file last-modified attribute. The moment the JSON model is republished, the file last-modified file attribute will be greater than the last-check. When this happens, we know the CacheElement is stale and we remove it from cache.

The stale logic also checks for the existence of a JSON model file. An unpublished (a.k.a. missing) file will immediately be considered stale, and as such removed from cache.

In order to make the cache invalidation check more performant and to minimize I/O operations with the file system, we only check for stale elements on (a) get from cache operation and (b) when a certain interval has passed since the previous stale check. This interval is configurable in Toolkit configuration under property name cacheMonitorSeconds. This value represents a period of time that is acceptable to retrieve potentially stale objects. Typically this value should be low - i.e. 5, 10 or 30 seconds or as long as you're comfortable with. A value of 0 will perform the stale check on all calls to the cache.get() method.

More information about possible values in the toolkit.properties file is available in post Installation and Configuration.

private boolean isStale(Element element) {
    CacheElement<Object> cacheElement = (CacheElement<Object>) element.getObjectValue();
    long lastCheck = cacheElement.getLastCheck();
    long now = System.currentTimeMillis();

    if (now - lastCheck > cacheMonitorInterval) {
        cacheElement.setLastCheck(now);
        Object value = cacheElement.getPayload();

        if (value instanceof IdentifiableObject) {
            IdentifiableObject identifiableObject = (IdentifiableObject) value;
            TcmUri tcmUri = identifiableObject.getTcmUri();
            PathMapper pathMapper = new PathMapper();
            File file = new File(pathMapper.getModelAbsolutePath(tcmUri));

            return !file.exists() || file.lastModified() > lastCheck;
        }
    }

    return false;
}



Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

I Have Gone Dark

Maybe it's the Holidays, but my mood has gone pretty dark. That is, regarding the look and feel of my computer and Tridion CME, of course. What I did was to dim the lights on the operating system, so I installed Placebo themes for Windows 7 . I went for the Ashtray look -- great name :) My VM looks now like this: But, once you change the theme on Windows, you should 'match' the theme of your applications. Some skin easily, some not. The Office suite has an in-built scheme, which can be set to Black , but it doesn't actually dim the ribbon tool bars -- it looks quite weird. Yahoo Messenger is skinnable, but you can't change the big white panels where you actually 'chat'. Skype is not skinnable at all. For Chrome, there are plenty of grey themes. Now i'm using Pro Grey . But then I got into changing the theme of websites. While very few offer skinnable interfaces (as GMail does), I had to find a way to darken the websites... Enter Stylish -- a pl

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when>         <c:otherwise>             Do something otherwise         </c:otherwise>     </c:choose> Att