|XP is just a number
> I'm wondering what performance penalty I'm paying for including documentation in my Perl CGI scripts, using either =pod or sequential #'s.
Well if you included many gigabytes of data in the POD you might probably be capable to experience an increased startup delay of your CGI because of a slow file system.
BUT you can always split your POD into a .pod file.
And of course there are ways to keep code persistent in memory and avoid reloading from the file system.
In reply to Re: Performance penalties of in-Perl docn vs compiled CGIs.