Displaying 1 result from an estimated 1 matches for "doprof".
Did you mean:
oprof
2009 Mar 03
1
profiler and loops
...one, the loop is wrapped in a function call. This shows the inability of
the profiler to point loops as responsible for bottlenecks. The coder of
script1 would not know what to do to improve on the script.
I have had a quick look in the code, and here are a few thoughts:
in the function "doprof" in eval.c, this loop write the call stack on
the profiler file:
for (cptr = R_GlobalContext; cptr; cptr = cptr->nextcontext) {
if ((cptr->callflag & (CTXT_FUNCTION | CTXT_BUILTIN))
&& TYPEOF(cptr->call) == LANGSXP) {
SEXP fun = CAR(cptr->call);...