Re: [R] Windows Memory Issues

2003-12-10 Thread Duncan Murdoch
On Wed, 10 Dec 2003 10:43:12 -0500, "JFRI (Jesper Frickmann)" <[EMAIL PROTECTED]> wrote : >I recommend you get the latest version 1.8.1 beta. I also had some >memory problems and that fixed it. 1.8.1 has been released, so there's no more beta. The release is available on CRAN (see http://cran.r-

RE: [R] Windows Memory Issues

2003-12-10 Thread JFRI (Jesper Frickmann)
I recommend you get the latest version 1.8.1 beta. I also had some memory problems and that fixed it. Kind regards, Jesper Frickmann Statistician, Quality Control Novozymes North America Inc. Tel. +1 919 494 3266 Fax +1 919 494 3460 __ [EMAIL PROTEC

RE: [R] Windows Memory Issues

2003-12-09 Thread Prof Brian Ripley
On Tue, 9 Dec 2003, Thomas Lumley wrote: > On Tue, 9 Dec 2003 [EMAIL PROTECTED] wrote: > > > Thanks for the reply. So are you saying that multiple calls to gc() frees > > up memory to Windows and then other processes can use that newly freed > > memory? > > No. You typically can't free memory

RE: [R] Windows Memory Issues

2003-12-09 Thread Prof Brian Ripley
On Tue, 9 Dec 2003 [EMAIL PROTECTED] wrote: > Thanks for the reply. So are you saying that multiple calls to gc() frees > up memory to Windows and then other processes can use that newly freed > memory? So multiple calls to gc() does not actually make more memory That is what I said. Why do pe

RE: [R] Windows Memory Issues

2003-12-09 Thread Thomas Lumley
On Tue, 9 Dec 2003 [EMAIL PROTECTED] wrote: > Thanks for the reply. So are you saying that multiple calls to gc() frees > up memory to Windows and then other processes can use that newly freed > memory? No. You typically can't free memory back to Windows (or many other OSes). >

RE: [R] Windows Memory Issues

2003-12-09 Thread Benjamin . STABLER
. And as I already said >(but has been excised below), this is not relevant to the next >version of >R anyway. > >BTW, the message below has been selectively edited, so please >consult the >original. > >> Message: 21 >> Date: Mon, 8 Dec 2003 09:51:12 -08

RE: [R] Windows Memory Issues

2003-12-09 Thread Pikounis, Bill
rbage collection. Thanks. > > Benjamin Stabler > Transportation Planning Analysis Unit > Oregon Department of Transportation > 555 13th Street NE, Suite 2 > Salem, OR 97301 Ph: 503-986-4104 > > ------- > > Message: 21 > Date: Mon, 8

Re: [R] Windows Memory Issues

2003-12-09 Thread Prof Brian Ripley
ge below has been selectively edited, so please consult the original. > Message: 21 > Date: Mon, 8 Dec 2003 09:51:12 -0800 (PST) > From: Douglas Grove <[EMAIL PROTECTED]> > Subject: Re: [R] Windows Memory Issues > To: Prof Brian Ripley <[EMAIL PROTECTED]> > Cc: [EMAIL P

Re: [R] Windows Memory Issues

2003-12-09 Thread Benjamin . STABLER
eet NE, Suite 2 Salem, OR 97301 Ph: 503-986-4104 --- Message: 21 Date: Mon, 8 Dec 2003 09:51:12 -0800 (PST) From: Douglas Grove <[EMAIL PROTECTED]> Subject: Re: [R] Windows Memory Issues To: Prof Brian Ripley <[EMAIL PROTECTED]> Cc: [

Re: [R] Windows Memory Issues

2003-12-08 Thread Douglas Grove
On Sat, 6 Dec 2003, Prof Brian Ripley wrote: > I think you misunderstand how R uses memory. gc() does not free up all > the memory used for the objects it frees, and repeated calls will free > more. Don't speculate about how memory management works: do your > homework! Are you saying that co

Re: [R] Windows Memory Issues

2003-12-06 Thread Jason Turner
Richard Pugh wrote: ... I have run into some issues regarding the way R handles its memory, especially on NT. ... Actually, you've run into NT's nasty memory management. Welcome! :) R-core have worked very hard to work around Windows memory issues, so they've probably got a better answer than

Re: [R] Windows Memory Issues

2003-12-06 Thread Prof Brian Ripley
I think you misunderstand how R uses memory. gc() does not free up all the memory used for the objects it frees, and repeated calls will free more. Don't speculate about how memory management works: do your homework! In any case, you are using an outdated version of R, and your first course o