similar to: shared mem advice

Full_Name: Wolfgang Huber Version: R-devel_2005-03-10 OS: alphaev68-dec-osf4.0f Submission from: (NULL) (62.253.128.15) This report concerns allocation of large (>2^31 byte) chunks of memory with R_alloc. I suspect it is a bug/typo but please don't hate me if it's actually a feature: In R, I can happily create large matrices: > a= matrix(0, nrow=191481, ncol=3063) > dim(a) [1]

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,

Hello!! I am a new user to puppet and I need to use puppet to install apc and change the size of apc.shm_size to 64. I have found a module here: https://github.com/ridonkulous/puppet-apc However, when I add the module in, it does not work. I get errors on the puppet code. Is there a way to just install the apc package normally and just use puppet code to change apc.shm_size? Thanks in

Dear R-help, I have been trying really hard to generate the following vector given the data (x) and parameter (alpha) efficiently. Let y be the output list, the aim is to produce the the following vector(y) with at least half the time used by the loop example below. y[1] = alpha * x[1] y[2] = alpha^2 * x[1] + alpha * x[2] y[3] = alpha^3 * x[1] + alpha^2 * x[2] + alpha * x[3] ..... below are

Hi, This problem started as of r73472 ("Merged in the rest of the basic ALTREP framework."); I tested r73471 and it did not exist. I'm building R devel on Ubuntu 16.04.3 LTS (64-bit), with the following flags: CC="gcc -std=gnu99 -fsanitize=address -fno-omit-frame-pointer" CFLAGS="-fno-omit-frame-pointer -g -O2 -Wall -pedantic -mtune=native" and using

Hi all, Why is the object size of an empty vector 40 bytes? (At least in 64-bit R.) object.size(integer(0)) # 40 bytes Reading R internals, it looks like it should be: * 4 bytes: sxpinfo header (= 32 bits) * 8 bytes: pointer to attributes * 8 bytes: pointer to next node * 8 bytes: pointer to previous node * 4 bytes: length * 4 bytes: true length = 36 bytes Where are the extra 4 bytes coming

Hi, I'm working with a fairly massive data set and I need to allocate memory beyond the 2GB limit. I'm using R 1.5.0 on a SunOS 5.8 machine (16 GB RAM). Has anyone been succesful at patching the code to get rid of the 2GB memory limit? (there are quite a few places in which vsize is an int or tested against INT_MAX). I'll appreciate any guidance you can provide. Thanks. Regards,

Full_Name: John Brzustowski Version: R-devel trunk and R-2.4.0 OS: linux Submission from: (NULL) (76.10.152.79) Here are two minor potential issues in pointer protection stack (PPS) code which could arise in debugging R with valgrind. Only the second could possibly cause a problem in normal use of R, and only under laughably implausible circumstances. (1) valgrind is given a wrong address when

Hi Jeremy, Thanks for your prompt response. I implemented your suggestion and added those lines to includes.h, recompiled and reinstalled the samba on the test machine. Unfortunately it made no difference. :-(. I added some debugging code and looked what happened : -------------------------------------------------------------------- DEBUG(4,("Trying sysv shmem open of size

Hello. I've been trying to wrap up the R_NilValue into OCaml-R. I nevertheless get a segfault. As I gathered, R_NilValue is declared in Rinternals.h: > /* Special Values */ > LibExtern SEXP R_NilValue; /* The nil object */ > LibExtern SEXP R_UnboundValue; /* Unbound marker */ > LibExtern SEXP R_MissingArg; /* Missing argument marker */ So, in my r_data.c

Dear Rdevelers, ? ? ?The following struct is in the Rinternals.h. I want to know ?the meanings of labels or names like "gp,mark,obj,named,trace....." . TKS! struct sxpinfo_struct { ? ? SEXPTYPE type ? ? ?: ?5;/* ==> (FUNSXP == 99) %% 2^5 == 3 == CLOSXP ? ? * -> warning: `type' is narrower than values ? ? * ? ? ? ? ? ? ?of its type ? ? * when SEXPTYPE was an enum

Hi. I've managed to make a *very* simple wrapper around the xts library for R into OCaml. (Need to be downloaded from CRAN for OCaml users, but I expect other wrapping to be fairly similar...). The good, good, good thing (from my humble point of view) is that all loading is done statically: Loading the R interpreter is done statically. Loading the xts library is done statically... etc...

Dear Developers, I've been struggling through writing R extension in C. I've been using an external pointer to store my data (please see sample below). I encountered a very weird erroneous behaviour: when I tried to use my external pointer to a structure holding several types of data, including SEXPs, I discovered that SEXPs change their types between returning from initialization

Hi, I'm trying to install RMySQL and I keep hitting errors. My computer is: uname -a Linux cricket 2.6.18-92.1.22.el5PAE #1 SMP Tue Dec 16 12:36:25 EST 2008 i686 i686 i386 GNU/Linux I have set the following environment settings: export PKG_LIBS="-L/usr/lib/mysql -lmysqlclient" export PKG_CPPFLAGS="-I/usr/include/mysql" I run the following command: R CMD INSTALL

Inside of the anyNA() function, it will use the legacy any(is.na()) code if x is an OBJECT(). If x is a vector of POSIXct, it will be an OBJECT(), but it is also TYPEOF(x) == REALSXP. Therefore, it will skip the faster ITERATE_BY_REGION, which is typically 5x faster in my testing. Is the OBJECT() condition really necessary, or could it be moved after the switch() for the individual TYPEOF(x)

I am now getting the occasional complaint about survival routines that are not able to handle big data.?? I looked in the manuals to try and update my understanding of max vector size, max matrix, max data set, etc; but it is either not there or I missed it (the latter more likely).?? Is it still .Machine$integer.max for everything??? Will that change??? Found where? I am going to need to go

Full_Name: stephen eglen Version: 1.0.0 OS: Unix (OSF/1) Submission from: (NULL) (129.215.238.26) Hi, in the documentation `Writing R Extensions', the section 3.6.1 (handling the effects of garbage collection) has the following typo: Protecting a SEXP pointer protexts ... Should that be `protects'? -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

as.name(as.name("ss")) gives an error in R (0.90 and earlier) but should of course give the same as simply as.name("ss") This reminds me of similar bug/problem... which I don't recall. Yes, I should build tests like these into "make test-Specific" .. Martin --please do not edit the information below-- Version: platform = sparc-sun-solaris2.5.1 arch =

>>>>> Harvey Smith >>>>> on Wed, 1 May 2019 03:20:55 -0400 writes: > Inside of the anyNA() function, it will use the legacy any(is.na()) code if > x is an OBJECT(). If x is a vector of POSIXct, it will be an OBJECT(), but > it is also TYPEOF(x) == REALSXP. Therefore, it will skip the faster > ITERATE_BY_REGION, which is typically 5x

Even though the FDA has no policies at all that limit our choices of statistical software, there is one defacto standard in place: reliance of the SAS transport file format for data submission (even though this format is deficient for this purpose, e.g., it does not even document value labels or units of measurement in a self-contained way). Because of the widespread use of SAS transport files in