making use of -profiler-

[László Sándor]

I am also confused by how to make the best use of -profiler-. I ran into an issue where my ado file spends the most time in a subroutine I defined, but I don't really see which commands therein took all that time. Out of the 141.187 seconds of overall runtime, 114.865 seconds are reported under the name of the subroutine, while other reported commands (most of them called by this subroutine) do not seem to add up to this. What goes unreported? E.g. I don't how much of the subroutine hung on on a largish -tabulate, summarize-…

[Maarten Buis]

For debugging of subroutines I wrote a Stata tip in the last Stata Journal: M.L. Buis (2014) "Stata tip 120: Certifying subroutines", The Stata Journal, 14(2), pp.449-450. You could use that trick to profile your sub-routine.

[László Sándor]

For debugging of subroutines I wrote a Stata tip in the last Stata Journal: M.L. Buis (2014) "Stata tip 120: Certifying subroutines", The Stata Journal, 14(2), pp.449-450. You could use that trick to profile your sub-routine.

Thanks, Maarten, this is useful, but I am confused whether this is relevant to which commands are profiled from within the subroutine. Some of those commands seem to appear in the profile, which e.g. _regress and _predict do not. I will read up on the profiler again, but I find it confusing and not very useful if Stata does not help me break down the runtime of the subroutine, only partially to an arbitrary subset of the commands called.