Oberdan Luiz May wrote:
Hello all,
Some time ago I started rewriting an old reporting system I've made,
trying to add some funcionalities and making it run faster. One of the main
problems is that, depending on the report choosen by the user, the result is
a VERY BIG list. I cant use mod_perl (at least for a while), so I was
thinking about using CGI::Simple instead of CGI and HTML::Template::Pro
instead of HTML::Template.
If you're generating a lot of data, then mod_perl wouldn't help much, and
focussing on CGI or HTML::Template is probably wrong. You would be much better
off making your reports paged or something like that. Have a look at
Data::Page, or CGI::Application::Plugin::Output::XSV (depending on how you
want to present the data).
Invoking HTML::Template usually doesn't take much more than 50-100ms
(depending on hardware, server load, etc). CGI takes even less time to do its
work.
For big reports, the bottleneck is in retrieving and manipulating the data,
not in script startup-time or Perl code execution.
Is there any known compatibility problem if I change these modules? If
its OK, which is the best way of changing HTML::Template to
HTML::Template::Pro?
As far as I know, CGI::Simple is a drop-in replacement for CGI (discounting
the html generation functions).
I don't have an objective opinion of HTML::Template::Pro (but subjectively,
the ::Pro makes me suspicious).
I would recommend profiling your reports to figure out where your code is
spending most of its time, then fixing those areas.
HTH,
Rhesa
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
