search for: vcell

Is it expected behavior for gc() to return shrinking values as it gets called multiple times? Here's what I've got: > gc() used (Mb) gc trigger (Mb) Ncells 221754 6.0 467875 12.5 Vcells 3760209 28.7 14880310 113.6 > gc() used (Mb) gc trigger (Mb) Ncells 221760 6.0 467875 12.5 Vcells 3016206 23.1 11904247 90.9 > gc() used (Mb) gc trigger (Mb) Ncells 221760 6.0 467875 12.5 Vcells 2420993 18.5 9523397 72.7 > gc() used (Mb) gc...

Dear all, I am working on a 64 bits Linux system. I issue the following R commands: > rm(list=ls()) # To remove all objects in the workspace. > gc() # To free memory. used (Mb) gc trigger (Mb) max used (Mb) Ncells 124250 6.7 350000 18.7 350000 18.7 Vcells 124547 1.0 786432 6.0 476934 3.7 > gc() # I had to do it again, don't know why! used (Mb) gc trigger (Mb) max used (Mb) Ncells 124257 6.7 350000 18.7 350000 18.7 Vcells 124574 1.0 786432 6.0 476934 3.7 > gc() # Just to be sure things have stabilized. used (Mb) gc trigger (Mb) max used...

...character data, gc() only seem to reflect the space needed for a vector of pointers to char, the space used for the character data itself is ... hidden!? Here the data: I have 6 MB heap, and can do > x <- rep(1, 350000); gc(); rm(x); gc() free total (Mb) Ncells 61034 250000 4.8 Vcells 350955 786432 6.0 free total (Mb) Ncells 61036 250000 4.8 Vcells 700956 786432 6.0 which is using about 2.67 MB RAM for double numbers. Trying for 3.05 MB fails (well, rep() obviously needs twice the memory, x <- double(700000) works) > x <- rep(1, 400000); gc(); rm(x); g...

...ject seems to be copied internally, doubling the memory requirement. See example below. Same for as.character() etc. Is this intended? Example: % R --vanilla > x <- double(1e7) > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 234019 6.3 467875 12.5 350000 9.4 Vcells 10103774 77.1 11476770 87.6 10104223 77.1 > x <- as.double(x) > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 234113 6.3 467875 12.5 350000 9.4 Vcells 10103790 77.1 21354156 163.0 20103818 153.4 However, couldn't this easily be avoided by letting as...

...se in memory consumed by new method expected? (having read R_Inferno I was, perhaps naively, expecting more of an improvement) ? or am I missing something (more than likely! ) Thanks M > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 786300 21.0 1265230 33.8 1166886 31.2 Vcells 948412 7.3 3244126 24.8 3766604 28.8 > cat("old version") Virtual size before call: 881692 user system elapsed 131.872 14.417 159.653 Virtual size after call: 899404 > 899404-881692 [1] 17712 ################## > gc() used (Mb) gc trigger (Mb) max us...

...t of 256Mb I'm able to call this function twice before running out of memory. After the allocation fails the GC is called & everything is freed, ie we end up with the same memory as before. Here is an example: > gc() used (Mb) gc trigger (Mb) Ncells 217415 5.9 467875 12.5 Vcells 63668 0.5 786432 6.0 > doit() > gc() used (Mb) gc trigger (Mb) Ncells 342932 9.2 667722 17.9 Vcells 7966401 60.8 14760173 112.7 > doit() > gc() used (Mb) gc trigger (Mb) Ncells 468373 12.6 818163 21.9 Vcells 15869121 121.1 22798845 174....

...is saved to an "xx.RData" it is still burdened, in some capacity, with the objects created in the function. Only deleting these objects at the end of the function ensures the realistic size of the returned object. Performing gc() after each of these short simulations shows that the "Vcells" that are accumulated in the function environment appear to remain after the function returns. These cached remains are then transferred to the .RData upon saving of the object(s). This is occurring quite broadly across the Windows 7 (R 2.10.1) and 64 Bit Ubuntu Linux (R 2.9.0) systems that I...

...n this situation. I verified that I don't have any objects in memory when R starts up, and that memory limits are set to NA. Here is some output: > ls() character(0) > mem.limits() nsize vsize NA NA > gc() used (Mb) gc trigger (Mb) Ncells 432197 11.6 531268 14.2 Vcells 116586 0.9 786432 6.0 > v<-rep(0,268435431) Error: cannot allocate vector of size 2097151 Kb > v<-rep(0,268435430) > object.size(v) [1] 2147483468 > gc() used (Mb) gc trigger (Mb) Ncells 432214 11.6 741108 19.8 Vcells 268552029 2048.9 268939773 2...

...rsion.string Version 2.3.0 (2006-04-24) > x<-matrix(nrow=44000,ncol=48000) > y<-matrix(nrow=44000,ncol=48000) > z<-matrix(nrow=44000,ncol=48000) > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 177801 9.5 407500 21.8 350000 18.7 Vcells -1126881981 24170.6 NA 24173.4 NA 24170.6 >

...sparc os solaris2.8 system sparc, solaris2.8 status major 1 minor 3.1 year 2001 month 08 day 31 language R A little example: Start a new section of R, with no objects: > ls() character(0) > gc() used (Mb) gc trigger (Mb) Ncells 187633 5.1 407500 10.9 Vcells 36061 0.3 786432 6.0 > And the top commands shows: PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 18068 gardar 1 32 0 15M 12M sleep 0:02 0.01% R.bin Creating few objects: > x <- numeric(1e7) > gc() used (Mb) gc trigger (Mb)...

hello, the question concerning to the memory used and g.c. after having removed objects. What is wrong? bevor ------- > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 313142 8.4 1801024 48.1 1835812 49.1 Vcells 809238 6.2 142909728 1090.4 178426948 1361.3 hier all attached objects detached and other no more used ones removed; also the objects which could change their size (like .Traceback) are checked; nothing unusual ----- after ------ > for (i in 1:30) gc() > gc(...

...ystem. >> I issue the following R commands: >> > rm(list=ls()) # To remove all objects in the workspace. >> > gc() # To free memory. >> used (Mb) gc trigger (Mb) max used (Mb) >> Ncells 124250 6.7 350000 18.7 350000 18.7 >> Vcells 124547 1.0 786432 6.0 476934 3.7 >> > gc() # I had to do it again, don't know why! >> used (Mb) gc trigger (Mb) max used (Mb) >> Ncells 124257 6.7 350000 18.7 350000 18.7 >> Vcells 124574 1.0 786432 6.0 476934 3.7 >> > gc() # Jus...

Dear All, I'm developing an R application running inside of a Java daemon on multiple threads, and interacting with the parent daemon via stdin and stdout. Everything works perfectly fine except for having some memory leaks somewhere. Simplified version of the R app: while (TRUE) { con <- file('stdin', open = 'r', blocking = TRUE) line <- scan(con,

...12.0780590098038, H.DKd=8 .25941049673737 ) = (Cost=3.16 , Err.Pwr=15.0, Err.Range=18.5, B/H=3.55) Garbage collection 170 = 160+7+3 (level 2) ... 147999 cons cells free (26%) 7.8 Mbytes of heap free (77%) used (Mb) gc trigger (Mb) limit (Mb) Ncells 417001 11.2 565000 15.1 16.1 Vcells 291029 2.3 1310720 10.0 20.0 total used free shared buffers cached Mem: 124948 93736 31212 0 17308 25824 -/+ buffers/cache: 50604 74344 Swap: 265032 8 265024 [1] 0 Gradient Design: Shi...

...ing=TRUE);line<-scan(con,what=character(0),nlines=1,quiet=TRUE);close(con);rm(con);a <- gc(); i <- i+1; if(i %% 1000 == 1) {cat('i=',i,'\\n'); print(a)} }" 11059 i= 1 used (Mb) gc trigger (Mb) max used (Mb) Ncells 83216 4.5 10000000 534.1 213529 11.5 Vcells 172923 1.4 16777216 128.0 562476 4.3 i= 1001 used (Mb) gc trigger (Mb) max used (Mb) Ncells 83255 4.5 10000000 534.1 213529 11.5 Vcells 172958 1.4 16777216 128.0 562476 4.3 ....... ............................................... ...........................................

I must be reading the help file for gc() wrong. I thought it said that gc(verbose=FALSE) will run the garbage collection without printing the Ncells/Vcells summary. However, this is what I get: gc(verbose = FALSE) used (Mb) gc trigger (Mb) max used (Mb) Ncells 267097 14.3 531268 28.4 531268 28.4 Vcells 429302 3.3 20829406 159.0 55923977 426.7 I'm embedding this in an Sweave/TeX file, so I *really* can't have this print...

...there is times to times a problem with allocating of objects of large size, for example 0.state (no objects yet created) ------------------------------------ > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 162070 4.4 350000 9.4 350000 9.4 Vcells 59921 0.5 786432 6.0 281974 2.2 1.state: let create now a vector of large size -------------------------------------------------- > my.vector<-rnorm(100000*500) > object.size(my.vector)/1024^2 [1] 381.4698 > 100000*500*8/1024^2 #calculate object.size...

...mber of calls to the internal function duplicate in the time interval (*Q1:* Are the units of the first 3 stats in bytes?) and from the gc() documentation, the two rows represent - ?"Ncells"? (_cons cells_), usually 28 bytes each on 32-bit systems and 56 bytes on 64-bit systems, - ?"Vcells"? (_vector cells_, 8 bytes each) (*Q2:* how are Ncells and Vcells related to small heap/large heap/memory in nodes?) And I guess the question that lead to these other questions is - *Q3:* I'd like to plot out the total amount of memory used over time, and I don't think Rprofmem() giv...

...w was gotten from R-2.6.2, compiled with --enable-memory-profiling on Ubuntu Linux. ======================================================================= >>> Code and output 1: > gc( ) used (Mb) gc trigger (Mb) max used (Mb) Ncells 131180 7.1 350000 18.7 350000 18.7 Vcells 136261 1.1 786432 6.0 573372 4.4 > nn <- 1000000 > ll <- list(xx = rnorm(nn), yy = rnorm(nn)) > tracemem(ll) [1] "<0x1e32c38>" > tracemem(ll$xx) [1] "<0x2af22e144010>" > tracemem(ll$yy) [1] "<0x2af22e8e6010>" > ll$xx...

...AM. It may be a useful developer tool for big-data problems. ------------------------ R version 2.4.1 (linux): > x <- matrix(as.integer(0), 1e+08, 3) > x <- x + 1 > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 233754 12.5 467875 25 350000 18.7 Vcells 300119431 2289.8 787870506 6011 750119944 5723.0 ------------------------ R version 2.6.0 (linux): > x <- matrix(as.integer(0), 1e+08, 3) > x <- x + 1 > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 137931 7.4 350000 18.7 350000 18.7 Vcells...