Installing ArgusCache
  1. Download the extensions from argusCache.com

    Download the two necessary extensions from ArgusCache.com. The files are so called lex files, (Lucee extension). You need to install one of the extensions in the server directory of the Lucee server you want to inspect and one in the Lucee WEB-INF directory for the ArgusCache application. You can install the two extensions like follows:

    Drop the argus-cache-1.0.0.xxx.lex file into the folder: lucee-server/deploy while Lucee is running. After a minute the file will be extracted and installed on the server. Please restart Lucee after the installation, especially if you update the ArgusCache version.

    The file argus-cache-client-1.0.0.xxx.lex you should drop into the folder: WEB-INF/lucee/deploy. After around a minute, you will find a folder called /arguscache inside your web root. When you now call yourdomain/arguscache, you need to log in with your Lucee web admin password.

    Login Dialog


  2. Log in into the ArgusCache frontend

    Once logged in, you will come to the settings page, which allows you to turn ArgusCache and different features on or off. The settings page looks like follows:

    The ArgusCache settings page


  3. The first thing you can do is to enable ArgusCache and the analysis of elements. On the lower right section of the settings page, you can also define which types of caches will be inspected/analyzed. From an ArgusCache perspective, you now have prepared everything necessary in order for the analysis to introspect your external resources.

  4. Go to the Application.cfc of the application you are about to tune and add the following lines for all the types you want ArgusCache to analyze:
    //this.cachedwithin["function"] = "smart";
    this.cachedwithin["http"]     = "smart";
    this.cachedwithin["query"]    = "smart";
    this.cachedwithin["include"]  = "smart";
    this.cachedwithin["file"]     = "smart";
    this.cachedwithin["invoke"]   = "smart";
    Please be aware, that activating functions could end up with loads of potential candidates, which might never be potential entries in the first place. As well know, that the functions could make out a big proportion of your code and that enabling ArgusCache for functions could massively slow down the execution of your code. We are working on additional functionality, which will allow you to easier inspect long running functions in CFML code. Amongst which are:
    • Analyze only resource calls that take longer than xxx microseconds
    • Analyze everything except the following directories
    • Analyze nothing except the following directories
    • Enabling of the analysis from the code
    When you now execute your application, you should see potential caching candidates (entries) and real candidates show up on the dashboard size. Check out the ArgusCache details page on more information on how ArgusCache works.


Social Media