similar to: --max-vsize and --max-nsize linux?

Martin M has suggested I widen this discussion to R-devel, and > I agree that we should increase them, > but I'm not sure at all about the amount. > > The default could even depend on the architecture (via "./configure").. Views, please. ------------- Begin Forwarded Message ------------- Is is not time we increased the defaults a bit? As the base gets bigger I hit

I am running R version ??? under Redhat 5.2. It seems as though the --nsize object has no effct on the size of the allocated Ncells as determined using gc(). Yes, I have that much data.... That is if I envoke R with R --vsize 100 --nsize 5000000 then type gc() I get free total Ncells 92202 200000 Vcells 12928414 13107200 Thanks Tony Long Ecology and Evolutionary Biology Steinhaus

Dear R-ers, somehow it is not possible to increase nsize to more than 20000k. When I specify e.g. > R --vsize=10M --nsize=21000K the result is: free total (Mb) Ncells 99658 350000 6.7 Vcells 1219173 1310720 10.0 Maybe I have overlooked s.th.... Marcus -- +------------------------------------------------------- | Marcus Eger | E-Mail: eger.m at gmx.de (NEW) |

Dear All, I am running R version 0.65.0 under a) Suse-Linux 6.1, and Suse-Linux 6.2, compiler gcc-2.95, CPUs pentium pro 200, 128MB, and pentium II 450, 128MB b) Solaris 5.7, compiler gcc-2.95, cpu SUN sparc, 4000MB When I set --nsize to more than 1M, R's internal storage management runs havoc. gc() indicates the requested sizes, but the overall process size is much too big: Running R with

Martin Morgan discussed this a year or so ago and as I recall bumped up these values to the current defaults. I don't recall details about why we didn't go higher -- maybe Martin does. I suspect the main concern would be with small memory machines in student labs and less developed countries. If there was a way on all platforms to identify how much memory is available that might help to

Hello, I'm using a 64bit Linux with 16GB of RAM. I'd like to limit the memory that the R process can use so I'm trying to use --max-vsize switch. However, it is seems that I can't enforce a limit above 2GB. shlomo at hippo:~$ uname -a Linux hippo 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux This WORKS: -------------------- shlomo at hippo:~$ R

Just wanted to start a discussion on whether R could ship with more appropriate GC parameters. Right now, loading the recommended package Matrix leads to: > library(Matrix) > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 1076796 57.6 1368491 73.1 1198505 64.1 Vcells 1671329 12.8 2685683 20.5 1932418 14.8 Results may vary, but here R needed 64MB of N cells and 15MB

Hi All, This is a very important issue. It would be very sad to leave most users unaware of a free speedup of this size. These options don't appear in the R --help output. They really should be added there. Additionally, if the garbage collector is working very hard, might it emit a note about better setting for these variables? It's not really my place to comment on design philosophy,

Full_Name: Markus Neteler Version: 1.0.0 OS: Linux 2.2.10/i686 Submission from: (NULL) (130.75.72.37) Hi, I wanted to "check" the R.GRASS GIS interface from Roger Bivand: http://www.geog.uni-hannover.de/grass/statsgrasslist.html using R CMD check --vsize=10M GRASS but: [error message shortened] > G <- gmeta() Error: heap memory (6144 Kb) exhausted [needed 1024 Kb more]

  R-devel, I am migrating from R.2.13.2 to R.2.15.1 and just realize that R command line options --max-nsize and --max-vsize are no longer supported along with the defunct of mem.limits(). To me, the function and options along with other two, --min-nsize and --min-vsize, are useful in allowing some explicit control of R memory usage. One benefit is that the setting of maximum boundary could

>>>>> Peter Haverty <haverty.peter at gene.com> >>>>> on Mon, 19 Jan 2015 08:50:08 -0800 writes: > Hi All, This is a very important issue. It would be very > sad to leave most users unaware of a free speedup of this > size. These options don't appear in the R --help > output. They really should be added there. Indeed,

On Thu, Jan 15, 2015 at 3:55 PM, Michael Lawrence <lawrence.michael at gene.com> wrote: > Just wanted to start a discussion on whether R could ship with more > appropriate GC parameters. I've been doing a number of similar measurements, and have come to the same conclusion. R is currently very conservative about memory usage, and this leads to unnecessarily poor performance on

Hi, I would like to have a software protection for my hardisk. I have some query regarding that (1) In Centos, is it possible to do a hardisk protection. Ex : Even if the hardisk is taken from a PC and used on another PC, it should not be executable. (2) Also if the entire binary of the source is mounted on a partition say /tmp, is it possible to make that mount point as protected,

Hi, I want to clone my hardisk containing the centos-5.3 OS and its swap region on to new raw hardisk via network either through ssh, tftp or ftp. How do i do that ? Is there any Tool for that or will DD command be sufficient.I know that dd command will have to be used on hardisk with already existing partitions and not on raw disk. Regards, Premraj M Disclaimer : This message is

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Dear Concerns, I have backup script which TAR the data, makes one copy on local hardisk and then FTP to another machine. Last few days i m facing problem with it. The cron job only makes the copy automatically on local disk but doesnot automatically FTP to another machine. I ran the script manually, the script runs successfully. For trouble shooting i displayed the output in some file and shown

I intended to create a share of a newly added hardisk(one partition) for public access. I declared the mount point in /etc/fstab as something like this, /dev/sdb1 /mnt/individual ext2 defaults 1 2 now, when i try to access the share from Window's browse list, it report that 'the share is not accessible, the network name cannot be found'. Any idea why? any clue would be appreciated.

The R memory docs say that the --*-vsize option takes an integer argument and then 'G', 'M', 'K', or 'k'. When I start R using R --max-vsize=10G I receive the warning: WARNING: --max-vsize=10G=10'M': too large and ignored The system that I'm working on is a 64-bit Sun server with 40G of memory. What is the correct syntax for this command? Daniel

Hi, In both R 2.13 and the SVN trunk, I observe odd behaviour with the --max-vsize command-line argument: 1. passing a largeish value (about 260M or greater) makes mem.limits() report NA for the vsize limit; gc() continues to report a value... 2. ...but that value (and the actual limit) is wrong by a factor of 8. I attach a patch for issue 2, lightly tested. I believe that fixing issue 1

I'd like to add S=<size> and W=<vsize> to the filenames in my Maildir storage for newly delivered mails. But I cannot find where I can make Dovecot's LDA add those. Anybody? http://wiki2.dovecot.org/MailboxFormat/Maildir says: A maildir filename with those fields would look something like: 1035478339.27041_118.foo.org,S=1000,W=1030:2,S which is exactly what I want, but it