Meta tags:
Headings (most frequently used words):
memory, profiling, in,
Text of the page (most frequently used words):
the (19), log (16), and (10), memory (9), trees (9), height (9), girth (9), data (8), #profiling (7), volume (7), this (6), not (6), that (6), profiler (5), when (5), glm (5), with (4), trace (4), does (4), tracemem (4), eval (4), use (3), for (3), output (3), large (3), vector (3), object (3), will (3), objects (3), information (3), call (3), formula (3), coefficients (3), intercept (3), memtrace (3), help (2), from (2), can (2), also (2), compiled (2), stack (2), sent (2), file (2), heap (2), summarize (2), rprofmem (2), printed (2), duplicated (2), functions (2), uses (2), 632 (2), 117 (2), 983 (2), 0x8b6d820 (2), null (2), residual (2), deviance (2), model (2), frame (2), has (2), rprof (2), three, experimental, additions, programs, reorganized, first, version, keep, code, documentation, time, sampling, separate, valgrind, level, using, thomas, lumley, 2006, tool, massif, defined, starts, stops, pure, any, enough, allocation, threshold, set, user, called, expand, timers, coexist, other, forms, yet, have, tools, getnewpage, r_memory_profiling, function, marks, copied, coercion, arithmetic, intended, tracking, accidental, copying, untrace, though, all, copies, controls, whether, tracing, example, below, see, duplicate, its, argument, but, copy, response, cannot, used, since, same, bit, work, such, environments, are, passed, reference, could, made, prettier, main, thing, decide, how, handle, files, multiple, may, being, traced, 0x8bfff28, 0x89b4c10, degrees, freedom, total, 309, 1855, aic, 0x895e230, 0x87a2898, default, 9877, 3393, 7082, tracingstate, untracemem, enable, option, writes, out, small, sizes, nodes, number, calls, interval, now, options, available, only, unix, moment, summaryrprof, rf_duplicate, true,
Text of the page (random words):
memory profiling memory profiling in r three experimental additions to help in profiling memory use in r programs this is reorganized from the first version to keep the code and documentation for the time sampling profiler rprof separate from the memory profiler rprofmem rprof has an option memory profiling when true the profiler also writes out information the small and large vector heap sizes memory in nodes and number of calls to rf_duplicate in the interval summaryrprof now has options to summarize this information this is available only on unix at the moment if r is compiled with enable memory profiling the function tracemem marks an object so that a stack trace will be printed when the object is duplicated or when it is copied by coercion or arithmetic functions this is intended for tracking accidental copying of large objects untracemem will untrace an object though not all copies of it and tracingstate controls whether tracing information is printed in the example below we see that lm does not duplicate its data argument but that glm does and that lm does copy the response vector data trees tracemem trees 1 lm log volume log height log girth data trees call lm formula log volume log height log girth data trees coefficients intercept log height log girth 6 632 1 117 1 983 glm log volume log height log girth data trees memtrace 0x8bfff28 0x8b6d820 glm memtrace 0x8b6d820 0x89b4c10 glm call glm formula log volume log height log girth data trees coefficients intercept log height log girth 6 632 1 117 1 983 degrees of freedom 30 total i e null 28 residual null deviance 8 309 residual deviance 0 1855 aic 62 71 tracemem trees volume 1 lm volume height girth data trees memtrace 0x895e230 0x87a2898 eval eval model frame default model frame eval eval lm call lm formula volume height girth data trees coefficients intercept height girth 57 9877 0 3393 4 7082 tracemem cannot be used on functions since it uses the same trace bit that trace uses and will not work on objects such as environments that are passed by reference and not duplicated the output for this could be made prettier and sent to a file the main thing to decide is how to handle files when multiple objects may be being traced if r is compiled with r_memory_profiling defined rprofmem starts and stops a pure memory use profiler a stack trace is sent to an output file on any large enough vector allocation threshold set by the user or when getnewpage is called to expand the r heap this profiler does not use timers and so can coexist with other forms of profiling i do not yet have tools to summarize the output valgrind can also help with memory profiling at the c level using tool massif thomas lumley 2006 8 1
|