G'day meetraz,

If you put this line 

INIT { exit }

[download]

before any other INIT blocks, your "app" should terminate before any runtime processing occurs.

I put together this quick and dirty test script (pm_1198271_prof_compile_only.pl): 

#!/usr/bin/env perl

use strict;
use warnings;
use autodie ':all';

use Moose;

BEGIN {
    print "BEGIN block\n";
}

sub should_not_run {
    print "&should_not_run ran!\n";
} 

should_not_run();

print "This shouldn't print\n";

INIT { exit }

INIT { print "This INIT shouldn't run.\n" }

[download]

Running that by itself: 

$ pm_1198271_prof_compile_only.pl
BEGIN block

[download]

Then doing as ++choroba suggested: 

$ perl -d:NYTProf pm_1198271_prof_compile_only.pl
BEGIN block
$ nytprofhtml
Reading nytprof.out
Processing nytprof.out data
Writing line reports to nytprof directory
 100% ... 
Extracting subroutine call data ...
Extracting subroutine links
Generating subroutine stack flame graph ...

[download]

View "nytprof/index.html" in the browser of your choice. The third table, "Source Code Files — ordered by exclusive time then name", should show what you're looking for, longest compile time first.

By using 'INIT { exit }', the profile results won't contain any runtime data; and it's just one line to remove when you've finished.

— Ken

In reply to Re: Profile compilation by kcott
in thread Profile compilation by meetraz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.