Re: Profiling Perl 6 code

2015-01-06 Thread Tobias Leich
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

Re: Profiling Perl 6 code

2015-01-05 Thread 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?

Re: Profiling Perl 6 code

2014-12-31 Thread Patrick R. Michaud
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

Profiling Perl 6 code

2014-12-30 Thread Gabor Szabo
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