If I understand what you're asking, Profile.print(format=:flat) should do the trick.
--Tim On Thursday, December 31, 2015 07:56:37 AM Cedric St-Jean wrote: > I like ProfileView.jl a lot, but there are times where a traditional flat > profiling output with `cumulative` would be more appropriate (eg. if I have > 10 expensive functions with 10 call sites each, it's hard to tell which > function to optimize in a heavily nested ProfileView visualization). > Profile.print gives me how many samples landed in this function exactly, > but I would like to know for each function F how many samples were caught > while F was on the call stack. Is there an easy way to get that? > > Cédric
