Re: Benchmarks for module compilation time

that's nice

When you are looking at the bigger picture you might want to take in account (and if that is interesting measure it too) that some of the modules rely heavily on AUTOLOAD and create some of their own functions or load additional modules in run time and based on the flow of your program.

Specifically CGI.pm is mostly a huge string called $AUTOLOADED_ROUTINES from where the rest of the code extracts the functions as they are needed.

Comment on Re: Benchmarks for module compilation time

Replies are listed 'Best First'.
Re^2: Benchmarks for module compilation time by itub (Priest) on Jul 20, 2005 at 12:56 UTC
POSIX is another example of a big module that uses AUTOLOAD. I wanted to test that one specifically because sometimes I hear that people are afraid of using it because it is "too big". However, for the "null use" of POSIX, it's one of the fastest to start up. I often use it just because I need a little function such as `floor` or `ceil`.	[reply] [d/l] [select]
Re^3: Benchmarks for module compilation time by szabgab (Priest) on Jul 20, 2005 at 14:03 UTC
speed is one thing. what might be also interesting is the memory footprint without POSIX, in "null use" and when using 1-2-3 functions.	[reply]