could be that the process was waiting for the user to select a file from a list, or some other input before proceeding. Would have to see what the overall performance of the system was at that point. It could also have been that the process was low on physical memory and there was a lot of paging going on.
Sent from my iPad On Nov 7, 2011, at 21:50, Rolf Turner <rolf.tur...@xtra.co.nz> wrote: > On 08/11/11 02:40, Joshua Wiley wrote: >> On Mon, Nov 7, 2011 at 5:32 AM, Alaios<ala...@yahoo.com> wrote: >>> So I just need to get the >>> >>> user system elapsed >>> 0.460 0.048 67.366 >>> >>> >>> user value and convert the seconds to days and then to hours ? Right? >>> >>> What about this elapsed field? >> It's all in seconds. Convert whatever fields you want. > > That being said, doesn't having an elapsed time of over 67 seconds, > when the actual calculation takes less than half a second, indicate > that something weird is going on? At the very least the R calculations > are fighting for resources with some other very greedy processes. > > cheers, > > Rolf Turner > > ______________________________________________ > R-help@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. ______________________________________________ R-help@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.
