Kjetil Halvorsen
2010-Nov-19 20:43 UTC
[R] ?summaryRprof running at 100% cpu for one hour ...
This is very strange. (Debian squeeze, R 2.12.0 compiled from source) I did some moderately large computation (including svd of a 560x50 matrix), running a few minutes, and R memory increasing to about 900MB on this 2 GB ram laptop. I had done Rprof(memory.profiling=TRUE) first. Then doing summaryRprof(). Then doing ?summaryRprof and then the computer running with one of two cores at 100% for more than an hour! Whats happening? (running R from within emacs-ess) Kjetil
On 19.11.2010 21:43, Kjetil Halvorsen wrote:> This is very strange. (Debian squeeze, R 2.12.0 compiled from source) > > I did some moderately large computation (including svd of a 560x50 matrix), > running a few minutes, and R memory increasing to about 900MB on this > 2 GB ram laptop. I had done Rprof(memory.profiling=TRUE) first. > Then doing summaryRprof(). > Then doing > ?summaryRprof > and then the computer running with one of two cores at 100% for more > than an hour! > > Whats happening?We do not know. What about sending a reproducible example? Best, Uwe> (running R from within emacs-ess) > Kjetil > > ______________________________________________ > R-help at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.
Kjetil Halvorsen
2010-Nov-21 00:30 UTC
[R] ?summaryRprof running at 100% cpu for one hour ...
see below. 2010/11/20 Uwe Ligges <ligges at statistik.tu-dortmund.de>:> > > On 19.11.2010 21:43, Kjetil Halvorsen wrote: >> >> This is very strange. (Debian squeeze, R 2.12.0 compiled from source) >> >> I did some moderately large computation (including svd of a 560x50 >> matrix), >> running a few minutes, and R memory increasing to about 900MB on this >> 2 GB ram laptop. I had done Rprof(memory.profiling=TRUE) first. >> Then doing summaryRprof(). >> Then doing >> ?summaryRprof >> and then the computer running with one of two cores at 100% for more >> than an hour! >> >> Whats happening? > > We do not know. What about sending a reproducible example?I will try. But how do I send this info when I have to kill the R-process from outside? kjetil> > Best, > Uwe > > >> (running R from within emacs-ess) >> Kjetil >> >> ______________________________________________ >> R-help at r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-help >> PLEASE do read the posting guide >> http://www.R-project.org/posting-guide.html >> and provide commented, minimal, self-contained, reproducible code. >
On 21.11.2010 01:30, Kjetil Halvorsen wrote:> see below. > > 2010/11/20 Uwe Ligges<ligges at statistik.tu-dortmund.de>: >> >> >> On 19.11.2010 21:43, Kjetil Halvorsen wrote: >>> >>> This is very strange. (Debian squeeze, R 2.12.0 compiled from source) >>> >>> I did some moderately large computation (including svd of a 560x50 >>> matrix), >>> running a few minutes, and R memory increasing to about 900MB on this >>> 2 GB ram laptop. I had done Rprof(memory.profiling=TRUE) first. >>> Then doing summaryRprof(). >>> Then doing >>> ?summaryRprof >>> and then the computer running with one of two cores at 100% for more >>> than an hour! >>> >>> Whats happening? >> >> We do not know. What about sending a reproducible example? > > I will try. But how do I send this infoWell, just send what you typed to get into that state ... Uwe> when I have to kill > the R-process from outside? > > kjetil > >> >> Best, >> Uwe >> >> >>> (running R from within emacs-ess) >>> Kjetil >>> >>> ______________________________________________ >>> R-help at r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-help >>> PLEASE do read the posting guide >>> http://www.R-project.org/posting-guide.html >>> and provide commented, minimal, self-contained, reproducible code. >>