> Using:
>
> summaryRprof(memory="both")
>
> did the trick, thank you. I had not been using that setting when calling
> summaryRprof.
>
> Thanks, Patrick
>
> 2010/11/20 Uwe Ligges <[email protected]>
>
>
>>
>> On 19.11.2010 21:48, Patrick Leyshock wrote:
>>
>>> I'm trying to configure Version 2.12.0 or R to do memory profiling.
>>>
>>> I've reconfigured the code:
>>>
>>> % ./compile --enable-memory-profiling=YES
>>>
>>> and verified that it's configured correctly by examining the output. I
>>> then
>>> rebuild R:
>>>
>>> % make
>>>
>>> Then I fire up R and run a script, using Rprof with the memory-profiling
>>> switch set to TRUE:
>>>
>>> Rprof("output", memory.profiling=TRUE);
>>> # a bunch of R code
>>> Rprof(NULL);
>>>
>>
>>
>> Wen I do
>>
>> summaryRprof(memory="both")
>>
>> I see an additional column ...
>>
>> but since you have not said what you tried exactly, we cannot help very
>> much.
>>
>> Uwe Ligges
>>
>>
>>
>> When I examine the output, however, using either R CMD Rprof from the
>>> shell,
>>> or summaryRprof from within R, the output I see is identical to the
>>> output I
>>> got when I ran R BEFORE I recompiled with memory profiling enabled.
>>>
>>> Anyone see something that I'm missing?
>>>
>>> Thanks, Patrick
>>>
>>> [[alternative HTML version deleted]]
>>>
>>> ______________________________________________
>>> [email protected] 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.
>>>
>>
>
[[alternative HTML version deleted]]
______________________________________________
[email protected] 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.
