similar to: memory profiling

Hi all, Where can I find an R binary version (>2.4.0 ) for windows that compiled with R_MEMORY_PROFILING? Within our application we are experiencing serious problems with memory usage. And being able to use "Rprofmem" and "tracemem" command seems like our best option. Thanks, Yoni [[alternative HTML version deleted]]

I'm trying to build R-devel with AMD's ACML. I downloaded version 3.0.0 64bit for gfortran (acml-3-0-0-gfortran-64bit.tgz) and copied the libraries to /usr/local/lib. When I configure R to build against the ACML library, how do I know if the library has been detected and will be used? I run 'configure' with the '--with-blas=-lacml' flag and am using gcc 4.0.2 (with

Hi (Roger), I saw the announcement of filehash v2.0 and the sentence "This development has lead to better file locking for concurrent access and faster reading and writing of data in general" caught my attention. What kind of file locking do you refer to here? I am looking for a mechanism that can be used to lock files for reading and/or writing, and I'd love to have a cross

When I build R-devel (or the alpha snapshots) on a system without makeinfo >= 4.7, I get a warning about not being able to build HTML/Info help pages after running 'configure' (but 'make' runs smoothly and there are no errors). However, when I run 'make install' I get an error, something like make[2]: Entering directory

In R 1.9.0 on Solaris/Sparc when I run, for example, install.packages("gregmisc", "~/R-local/lib"), instead of installing the `gregmisc' package in the directory /users/student/rpeng/R-local/lib the package gets installed in /users/student/rpeng/\~/R-local/lib, so the directory \~ is created in my home directory. This doesn't happen to me on Linux or Windows so I

Hi All, i have a problem in understanding what the assignment operator '<-' really is doing. If i create two numeric arrays in R and copy one into the other with '<-' and afterwards change one array by calling a C function, both arrays are changed! The problem I am facing can easily be seen in the following example: (The following R code and the C function is attached and

Hi, I've noticed that as.vector() always allocates a new object, e.g. > x <- 1:10; > x <- as.vector(x); > tracemem(x); [1] "<0x0000000005622db8" > x <- as.vector(x); tracemem[0x0000000005622db8 -> 0x0000000005622ec0]: as.vector > x <- as.vector(x); tracemem[0x0000000005622ec0 -> 0x0000000005622f18]: as.vector > x <- as.vector(x);

The 'cacher' package contains a set of routines for caching statistical analyses. The idea is that an analysis stored in a file (say, 'foo.R') is run and the results of the evaluated expressions are cached in a database. These cached results can subsequently be packaged up and distributed over the interweb. I've just uploaded to CRAN version 0.1-2 of the 'cacher'

The 'cacher' package contains a set of routines for caching statistical analyses. The idea is that an analysis stored in a file (say, 'foo.R') is run and the results of the evaluated expressions are cached in a database. These cached results can subsequently be packaged up and distributed over the interweb. I've just uploaded to CRAN version 0.1-2 of the 'cacher'

Hi all, I've been trying to get a better handle on what manipulations lead R to duplicate a vector, creating small experiments and using tracemem to observe what happens (all in 2.15.1). That's lead me to a few questions, illustrated using the snippet below. x <- 1:10 tracemem(x) # [1] "<0x1058f8238>" x[5] <- 5 # tracemem[0x1058f8238 -> 0x105994ab0]: x[11] <-

I've noticed recently that 'update.packages' and 'install.packages' seem to not do tilde expansion anymore, i.e. when I run update.packages("~/R-local/lib") on R-alpha (r41043) I get the message /home/rpeng/install/R-alpha/lib64/R/bin/INSTALL: line 304: cd: ~/R-local/lib: No such file or directory and the package is subsequently installed in the current working

My understanding is that R will not make copies of lists if there is only one reference to the object. However, I've encountered a case where R does make copies, even though (I think) there should be only one reference to the object. I hope that someone could shed some light on why this is happening. I'll start with a simple example. Below, x is a list with one element, and changing that

The Rprofmem facility is currently enabled only if the configuration option --enable-memory-profiling is used. However, the overhead of having it enabled is negligible when profiling is not actually being done, and can easily be made even smaller. So I think it ought to be enabled all the time. I've attached a patch doing this, which also makes a number of other improvements to Rprofmem,

I have just uploaded a package to CRAN called `gpclib' for clipping large and complex polygons. This package provides an R interface to Alan Murta's very fast General Polygon Clipper library (written in C), which has an optimized version of the Vatti algorithm. Not all features of Murta's library are implemented -- right now you can do intersections, differences, and unions. There

I have just uploaded a package to CRAN called `gpclib' for clipping large and complex polygons. This package provides an R interface to Alan Murta's very fast General Polygon Clipper library (written in C), which has an optimized version of the Vatti algorithm. Not all features of Murta's library are implemented -- right now you can do intersections, differences, and unions. There

Hi, $ R --vanilla R version 2.14.1 (2011-12-22) Platform: i686-pc-linux-gnu (32-bit) > DF = data.frame(a=1:3,b=4:6) > DF a b 1 1 4 2 2 5 3 3 6 > tracemem(DF) [1] "<0x8898098>" > names(DF)[2]="B" tracemem[0x8898098 -> 0x8763e18]: tracemem[0x8763e18 -> 0x8766be8]: tracemem[0x8766be8 -> 0x8766b68]: > DF a B 1 1 4 2 2 5 3 3 6 > Are those 3

Since compiling R 2.5.0 from source on my Mac (PowerBook) I've noticed some strange behavior when plotting. I'm not sure if it's a problem with my setup/compilation because I feel like a problem as basic as this one would have been reported already. I'm running R with X11 and R was built with gcc 4.0.1. Basically, I run > plot(0, 0) > dev.off() X11 4 Warning message:

Are the functions 'R_Unserialize' and 'R_InitFileInPStream' allowed to be used in R packages? I guess I'm just not clear on the implications of this comment in 'Rinternals.h': /* The connection interface is not yet available to packages. To allow limited use of connection pointers this defines the opaque pointer type. */ I have a function in the

Hi Expert I want to use dtrace to monitor the content change of one file. I made following scripts, #!/usr/sbin/dtrace -s inline int MYPID = $1; syscall::write:entry /pid == MYPID/ { tracemem(arg1, arg2); printf("\n"); } It always has an following error bash-3.00$ sudo dumpFIFO.dtrace 3836 dtrace: failed to compile script ./dumpFIFO.dtrace: line 19: tracemem( ) argument #2

Is putting a variable into a list a deep copy (and is tracemem the correct way to confirm)? warmstrong at krypton:~/dvl/R.packages$ R > x <- rnorm(1000) > tracemem(x) [1] "<0x3214c90>" > x.list <- list(x.in.list=x) tracemem[0x3214c90 -> 0x2af0a20]: > Is it possible to put a variable into a list without causing a deep copy (i.e. if you _really_ want the