{"id":46,"date":"2006-04-04T16:13:48","date_gmt":"2006-04-04T21:13:48","guid":{"rendered":"http:\/\/raffy.ch\/blog\/?p=46"},"modified":"2006-04-04T16:17:14","modified_gmt":"2006-04-04T21:17:14","slug":"perl-performance-optimization","status":"publish","type":"post","link":"https:\/\/raffy.ch\/blog\/2006\/04\/04\/perl-performance-optimization\/","title":{"rendered":"Perl Performance Optimization"},"content":{"rendered":"

I was working on AfterGlow<\/a> the other night and I realized that adding feature after feature starts to slow down the thing quite a bit (you need to be a genious to figure that one out!). So that prompted me to look for Perl performance analyzers and indeed I found something that’s pretty useful.<\/p>\n

Run your perl script with: perl -d:DProf<\/code> and then run dprofpp<\/code>. This will show you how much time was spent in each of the subroutines. It helped me pinpoint that most of the time was spent in the getColor() call. The logical solution was to introduce a cache for the colors and guess what – AfterGlow 1.5.1 will be faster \ud83d\ude09<\/p>\n

This is a sample output of dprofpp:<\/p>\n

Total Elapsed Time = 11.69959 Seconds
\n User+System Time = 8.969595 Seconds
\nExclusive Times
\n%Time ExclSec CumulS #Calls sec\/call Csec\/c Name
\n 81.5 7.310 9.900 120000 0.0001 0.0001 main::getColor
\n 29.1 2.615 2.615 116993 0.0000 0.0000 main::subnet
\n 0.89 0.080 0.080 20000 0.0000 0.0000 main::getEventName
\n 0.22 0.020 0.020 20000 0.0000 0.0000 main::getSourceName
\n 0.22 0.020 0.020 20000 0.0000 0.0000 main::getTargetName
\n 0.11 0.010 0.010 1 0.0100 0.0100 main::BEGIN
\n 0.00 - -0.000 1 - - Exporter::import
\n 0.00 - -0.000 1 - - Getopt::Std::getopts
\n 0.00 - -0.000 1 - - main::propertyfile
\n 0.00 - -0.000 1 - - main::init
\n - - -0.025 116993 - - main::field
\n<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

I was working on AfterGlow the other night and I realized that adding feature after feature starts to slow down the thing quite a bit (you need to be a genious to figure that one out!). So that prompted me to look for Perl performance analyzers and indeed I found something that’s pretty useful. Run […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-46","post","type-post","status-publish","format-standard","hentry","category-programming"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t