R benchmarking made easy. The package contains a number of benchmarks, heavily based on the benchmarks at http://r.research.att.com/benchmarks/R-benchmark-25.R, for assessing the speed of your system.
A straightforward way of speeding up your analysis is to buy a better computer. Modern desktops are relatively cheap, especially compared to user time. However, it isn’t clear if upgrading your computing is worth the cost. The benchmarkme package provides a set of benchmarks to help quantify your system. More importantly, it allows you to compare your timings with other systems.
The package is on CRAN and can be installed in the usual way
There are two groups of benchmarks:
benchmark_std(): this benchmarks numerical operations such as loops and matrix operations. The benchmark comprises of three separate benchmarks:
benchmark_io(): this benchmarks reading and writing a 5 / 50, MB csv file.
This benchmarks numerical operations such as loops and matrix operations. This benchmark comprises of three separate benchmarks:
matrix_cal. If you have less than 3GB of RAM (run
get_ram() to find out how much is available on your system), then you should kill any memory hungry applications, e.g. firefox, and set
runs = 1 as an argument.
To benchmark your system, use
and upload your results
You can compare your results to other users via
This function benchmarks reading and writing a 5MB or 50MB (if you have less than 4GB of RAM, reduce the number of
runs to 1). Run the benchmark using
By default the files are written to a temporary directory generated
which depends on the value of
You can alter this to via the
tmpdir argument. This is useful for comparing hard drive access to a network drive.
The benchmark functions above have a parallel option - just simply specify the number of cores you want to test. For example to test using four cores
The process for the parallel benchmarks of the pseudo function
benchmark_x(cores = n) is: - initialise the parallel environment - Start timer - Run job x in core 1, 2, …, n simultaneously - when all jobs finish stop timer - stop parallel environment This procedure is repeat
This package was started around 2015. However, multiple changes in the byte compiler over the last few years, has made it very difficult to use previous results. So we have to start from scratch.
The previous data can be obtained via
The package has a few useful functions for extracting system specs:
The above functions have been tested on a number of systems. If they don’t work on your system, please raise GitHub issue.
A summary of the uploaded data sets is available in the benchmarkmeData package
A column of this data set, contains the unique identifier returned by the
Two objects are uploaded:
Sys.info() does include the user and nodenames. In the public release of the data, this information will be removed. If you don’t wish to upload certain information, just set the corresponding argument, i.e.
Development of this package was supported by Jumping Rivers