Re: Memory problems with Xpose

From: Leonid Gibiansky Date: January 14, 2012 technical Source: mail-archive.com
Toufigh, In my experience, R on 32 bit system crashes when it reaches about 1.4 GB of memory (even on a 4 GB system). You can see it in the task manager (observe how memory use increases until R crashes). I was not able to do anything with it except to switch to a 64 bit system, where the limit is much-much larger. Sometimes it helps to start from the fresh system (starting clean R run): if you you to save the work space and start from the saved one, this may explain why you had no problems in the earlier stages of the project when the work space was smaller. Leonid -------------------------------------- Leonid Gibiansky, Ph.D. President, QuantPharm LLC web: www.quantpharm.com e-mail: LGibiansky at quantpharm.com tel: (301) 767 5566
Quoted reply history
On 1/13/2012 10:53 AM, Toufigh Gordi wrote: > Hi Justin (and others), > > My computer has 3GB, running Windows 7 on a 32 bit machine. The interesting thing is that this is happening in the middle of a modeling project and so far there have been no issues. I have now tried it on an XP machine with 4GB of Ram and get the same message there. Interestingly, the whole folder with about 50 tested models and associated files is only 360 MB, so my RAM is over 10 time that. My R version is 2.14.0 (2011-10-31). I'll see if a newer version is available. > > Toufigh > > *From:*Justin Wilkins [mailto:[email protected]] > *Sent:* Friday, January 13, 2012 1:23 AM > *To:* Toufigh Gordi > *Cc:* [email protected] > *Subject:* Re: [NMusers] Memory problems with Xpose > > Dear Toufigh, > > I guess you've got a relatively large model and/or dataset - R has bumped up against its memory limit under your version of Windows (which I'm assuming you're using based on the error message). Which version are you using? 32-bit or 64-bit? > > To support what Andy and Jeroen have suggested, the solutions are typically to get more RAM, upgrade R, upgrade to a 64-bit OS if you aren't already running on one, or to reduce the scope of the problem. You could accomplish the latter by running the parameter vs covariate comparisons by hand, or by doing them in smaller batches. See help(xpose.prefs-class) for details related to changing the definitions of the parameters and covariates in the Xvardef section of an Xpose data object - shortening the vectors of parameters (parms) and covariates will reduce the dimensionality or the problem. > > You could also try upping the memory limit (using memory.limit), but this may not work. There's a short discussion of Windows memory limits in R here: http://cran.r-project.org/bin/windows/base/rw-FAQ.html#There-seems-to-be-a-limit-on-the-memory-it-uses_0021 > > Hope this helps! > > Best > > Justin > > On Jan 13, 2012, at 9:28 AM, Toufigh Gordi wrote: > > Hi, > > I am trying to plot model parameters vs. covariates suing Xpose. The data file is rather large and I get the following message: > > In initialize(value, ...) : > > Reached total allocation of 1535Mb: see help(memory.size) > > 2: In initialize(value, ...) : > > Reached total allocation of 1535Mb: see help(memory.size) > > Error in print(parm.vs.cov(.cur.db)) : > > error in evaluating the argument 'x' in selecting a method for function 'print': Error: cannot allocate vector of size 171 Kb > > Can anybody offer a remedy? > > Thanks! > > Toufigh > > -- > > Justin Wilkins, PhD > > Exprimo NV > > Tel: > > +41 (0) 81 599 23 82 > > Mobile: > > +41 (0) 76 561 09 49 > > E-mail: > > [email protected] <mailto:[email protected]> > > Web: > > www.exprimo.com http://www.exprimo.com/ > > This e-mail is confidential. It is also privileged or otherwise protected by work product immunity or other legal rules. The information is intended to be for use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. You should therefore delete this message from your computer system. If you have received the message in error, please notify us by reply e-mail. The integrity and security of this message cannot be guaranteed on the Internet. > > Thank you for your co-operation.
Jan 13, 2012 Toufigh Gordi Memory problems with Xpose
Jan 13, 2012 Jeroen Elassaiss-Schaap RE: Memory problems with Xpose
Jan 13, 2012 Jeroen Elassaiss-Schaap RE: Memory problems with Xpose
Jan 13, 2012 Andrew Hooker RE: Memory problems with Xpose
Jan 13, 2012 Justin Wilkins Re: Memory problems with Xpose
Jan 13, 2012 Jean Lavigne RE: Memory problems with Xpose
Jan 14, 2012 Leonid Gibiansky Re: Memory problems with Xpose