The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Common Subexpression Elimination

Background

Common Subexpression Elimination is an optimization that searches for instances of identical expressions, and replaces them with a single variable holding the computed value.

For instance, consider the following code:

a <- 1 / (8 + 8 + 1 + 9 * 1 ^ 8)
b <- (8 + 8 + 1 + 9 * 1 ^ 8) * 2

This code computes twice 8 + 8 + 1 + 9 * 1 ^ 8, this could be evaluated once, assigned to a new variable, and used twice. Like, for example:

cs_1 <- (8 + 8 + 1 + 9 * 1 ^ 8)
a <-  1 / cs_1
b <- cs_1 * 2

Example

Consider the following example:

code <- paste(
  "a <- b <- c <- 1",
  "for (i in 1:1000) {",
  "  a <- a ^ i ^ c",
  "  b <- b * i ^ c",
  "  c <- c + i ^ c",
  "}",
  sep = "\n"
)
cat(code)

## a <- b <- c <- 1
## for (i in 1:1000) {
##   a <- a ^ i ^ c
##   b <- b * i ^ c
##   c <- c + i ^ c
## }

Then, the automatically optimized code would be:

opt_code <- opt_common_subexpr(list(code))
cat(opt_code$codes[[1]])

## a <- b <- c <- 1
## for (i in 1:1000) {
##   cs_1 <- i ^ c
##   a <- a ^ cs_1
##   b <- b * cs_1
##   c <- c + cs_1
## }

And if we measure the execution time of each one, and the speed-up:

bmark_res <- microbenchmark({
  eval(parse(text = code))
}, {
  eval(parse(text = opt_code))
})
autoplot(bmark_res)

speed_up(bmark_res)

##            Min.  1st Qu.   Median     Mean  3rd Qu.     Max.
## Expr_2 72.71942 71.45588 57.04165 60.62192 54.46368 56.38661

Implementation

The opt_common_subexpr will first detect different “environments”, i.e., separate between function definitions and parent environment. Then, for each environment it will detect all those subexpressions in common between at least two expressions. If between two occurrences of the same subexpression, a variable involved in the subexpression is reassigned or a function is called (it can change the environment), then for these two occurrences the optimization is not performed. For all those remaining common subexpressions, the first common parent expression will be detected, a new variable called cs_# will be created in the parent expression, and replaced in each call to the subexpression.

To-Do

• Consider functions as common subexpressions?

  This can have an issue if the common function call returns random values.

  For example:

  a <-rnorm(1) * 8
  b <-rnorm(1) * 18
  

  Will be wrongly optimized to:

  cs_1 <- rnorm(1)
  a <-cs_1 * 8
  b <-cs_1 * 18
  

• Use information about which functions modify their parent env?

  If the optimizer knows which functions modify their parent env, then function calls won't stop optimization

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.