R-caching (and scheduling)

This is in preparation for running a custom Shiny server. We want to accelerate the server by using caching. In the this post we take a look at a candidate caching package.

In this post we’ll explore a the package DataCache. It is a very useful package, however, I found that for some reason the provided weather data example was not working.  So I wanted to simulate a  datafeed using a scheduler, preferably within R. There is a scheduler package for R tcltk2. It worked for me from the command line, however when running this in RStudio or Rscript there is a small complication, which we will cover further below.

The data function here  outputs the system time, using Sys.time(). When it is cached it uses a previous version of the cached time, therefore it is is smaller than the current Sys.time(). In general

Current time >=Cached time  .

Let’s look at the output first:

So we can see that it works. Basically, the scheduler does a cycle ~ every 200ms, whereas the Cached time is only updated every second, which implies that the update happens after 5 = 1000ms/200ms cycles.

Let’s discuss the code. We have three parts:

  1. Preparations: Loading packages, setting options:
  2. Define the functions for caching:  the datafeed and custom frequency function :
  3. Define the scheduler:

The final part is only necessary when not running the code in the R command line i.e., when using it in Rstudio or Rscript. This is necessary for the scheduler to work.  There are other ways to define schedulers, which are more robust, but less readable than the tclTaskSchedule, therefore for simplicity’s sake I chose tclTaskSchedule for this post.

 

Final comment: The main hurdle to understanding the way DataCache works are these two points:

  • data.cache expects a function. If we want more than one cache we can can e.g. distinguish these by using a variable name varName1, and wrap the datafeed_getTime(varName1) call  in a anonymous function

    That variable name is then used in datafeed_getTime to define under which name the value is saved, this is done here:

This means because we define varName1 = ‘test1’ that  the cached variable for this varName is Mycached.test1

So here is the entire code (for easy copy and pasting):