Devel::NYTProf - Perl profiling links needed

A conversation on IRC this morning...

07:46 XXXX damn... is it normal for DProf/Profiler to not work correctly with moose stuff?
07:46 aaaa people still use dprof?
07:47 XXXX people who might not be aware of alternatives, sure
07:48 XXXX what would you suggest instead then?
07:49 aaaa Devel::NTYProf is THE profiller these days :)
07:52 XXXX unfortunately googling perl profiling doesn't take you anywhere near it :(

So, I'd like to talk about Perl profiling, or even profiling Perl. Devel::NYTProf doesn't make the claim that it is THE Perl profiler, but it really does seem to be the best profiler for Perl that is currently available.

If you've not come across Devel::NYTProf the Perl profiler please go and give it at try.

If like me you think it's fantastic, please link to from your website with some appropriate link words, so we can let Google know about it, and therefor the rest of the world.


Whilst I wholly agree that Devel::NYTProf is the profiler for Perl now I don't think creating loads of blog entries simply referring to it is of any great use. In fact, it may become annoying for people searching for useful information on Devel::NYTProf. By all means write a blog entry about Devel::NYTProf but at least make it something useful to others.

I seem to recollect Tim Bunce was calling for examples of code Devel::NYTProf had highlighted as time consuming and how it was changed to speed it up, for one of his talks. This might be a good way to mention Devel::NYTProf and at the same time help Tim.

Indeed, since this is a shared website, please don't penalize the rest of us by making search engines think that the domain is for link spam.

Everyone thinks this stuff is okay and tolerable when it's a topic they care about, but most everyone complains when it's a topic that they don't care about.

The way to let people know about it is not to link to it. It's to show them how to use it and why it worked for you.

Next time I just won't bother, and I'll leave you all to work out why it is that newbies find Perl hard / unfriendly.

I don't think that is the reaction that brian was looking for nor do I think it is warranted.

Post about what you want to post about. brian was more concerned that this blog doesn't become a link infestation.

One way to show people a module is out there, and to get it into the search engines, is to blog about it. It could be a simple "Devel::NYTProf is the bomb" post or it could be a real world "I had a problem and this is how Devel::NYTProf solved it".

I can't speak for brian, but by all means advocate the module!

Next time I just won't bother, and I'll leave you all to work out why it is that newbies find Perl hard / unfriendly.

Please don't take the comments this way. I was only suggesting if people mentioned Devel::NYTProf they should attempt to be a little more constructive about it than simply adding a link to it.

Devel::NYTProf is in a similar situation to many modules on CPAN; it is one of many looking like they do a similar job. Unless you are prepared to read the reviews and look at the CPAN test reports it can be difficult to know which one to start with. Interestingly, a search on CPAN for "profile" does not return Devel::NYTProf in the first few pages which is of more interest to me - presumably because "profile" is not in the name.

I think Devel::NYTProf is an excellent module and it has certainly helped me. I'm certainly not against anyone promoting it.

Leave a comment

About Ranguard

user-pic London Perl developer