comment on

My team has a problem. We have a fairly large code base, and we've been having problems getting the various profilers to work on it. In some cases, the profilers crash and burn. In other cases, we get numbers that we just don't trust.

We're embarking on an effort to fix one or more (but probably only one) of the existing profilers, with the intent of contributing any general fixes back to CPAN. To gear up, we're looking around for current information about what kinds of things (eg., Perl constructs, specific modules, etc.) confuse the current generation of profilers. (We do a few marginally legal things with typeglobs, for example.) We're reading up on existing bug reports, but field reports are useful, too.

If you've run into difficulties getting Perl code to profile, especially if you've worked around those problems, please post what details you can. Even "I suspect the problem may have been _____" might help. The info we gather will help us craft experiments and test cases, so that we can make the best of our limited time and budget.

Thanks.

Edited by planetscape - moved to Seekers of Perl Wisdom

In reply to Gathering data on Profiling woes by dws

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks