When working with big data sets, RAM conservation is critically important. However, it is not always enough to just monitor the size of the objects created. So-called "copy-on-modify" behavior, characteristic of R, means that some expressions or functions may require an unexpectedly large amount of RAM overhead. For example, replacing a single value in a matrix duplicates that matrix in the back-end, making this task require twice as much RAM as that used by the matrix itself. This package makes it easy to monitor the total and peak RAM used so that developers can quickly identify and eliminate RAM hungry code.
| Version: | 1.0.2 |
| Depends: | R (≥ 3.2.2) |
| Suggests: | knitr, rmarkdown |
| Published: | 2017-01-16 |
| DOI: | 10.32614/CRAN.package.peakRAM |
| Author: | Thomas Quinn [aut, cre] |
| Maintainer: | Thomas Quinn <contacttomquinn at gmail.com> |
| BugReports: | http://github.com/tpq/peakRAM/issues |
| License: | GPL-2 |
| URL: | http://github.com/tpq/peakRAM |
| NeedsCompilation: | no |
| Materials: | README, NEWS |
| CRAN checks: | peakRAM results |
| Reference manual: | peakRAM.html , peakRAM.pdf |
| Vignettes: |
Tracking Peak RAM Use and Minimizing Overhead (source, R code) |
| Package source: | peakRAM_1.0.2.tar.gz |
| Windows binaries: | r-devel: peakRAM_1.0.2.zip, r-release: peakRAM_1.0.2.zip, r-oldrel: peakRAM_1.0.2.zip |
| macOS binaries: | r-release (arm64): peakRAM_1.0.2.tgz, r-oldrel (arm64): peakRAM_1.0.2.tgz, r-release (x86_64): peakRAM_1.0.2.tgz, r-oldrel (x86_64): peakRAM_1.0.2.tgz |
| Old sources: | peakRAM archive |
| Reverse suggests: | SurprisalAnalysis |
Please use the canonical form https://CRAN.R-project.org/package=peakRAM to link to this page.
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.