There is only one file to look for: profile-\d+.html in your cwd. And as a side note: do not profile code that runs that long. 8 minutes of execution will produce an html file (with a json blob) of several hundreds of megabytes. Your browser won't cope with that. Try to profile only for a single html file. Optimize your code (or report strange things), and then perhaps move to another html file.
Am 06.01.2015 um 08:05 schrieb Gabor Szabo: > I tried that and while it was running my hard disk ran out of space. I > am not sure if it is related, but the process crashed and I could not > find if it created anything on the disk. Before trying again, I'd like > to remove anything it might have created. Where should I look for its > temporary files? > > Gabor > > On Wed, Dec 31, 2014 at 11:29 AM, Patrick R. Michaud > <pmich...@pobox.com <mailto:pmich...@pobox.com>> wrote: > > If you're running Rakudo on MoarVM, try the --profile option. It > will create an HTML file that shows a lot of useful information, > including time spent in each routine, call graphs, GC allocations, > etc. > > Pm > > On Wed, Dec 31, 2014 at 09:35:33AM +0200, Gabor Szabo wrote: > > The Perl 6 Maven site is a static site generated by some Perl 6 > code. > > Currently it takes about 8 minutes to regenerate the 270 pages > of the site > > which is quite frustrating. > > > > Is there already a tool I could use to profile my code to see > which part > > takes the longest time > > so I can focus my optimization efforts in the most problematic area? > > > > regards > > Gabor > >
