Oberdan Luiz May wrote: > 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.
If it's the size of the report that's a problem, then the slowness might have nothing to do with your server. It might just take a long time to send that much HTML over the wire. Consider using something like mod_deflate (if you're using Apache2). > I cant use mod_perl (at least for a while) Can you use FastCGI? >, so I was > thinking about using CGI::Simple instead of CGI and HTML::Template::Pro > instead of HTML::Template. Have you done any benchmarking of your application to know that your bottle necks are CGI.pm and HTML::Template? You could wind up doing a lot of work just to make a %1 gain in speed that won't be noticed by anyone. I can see maybe CGI.pm since it's a big module and can take a while to load everytime in a non-persistant environment. But finding an application where the templating is a bottle neck is pretty rare. Make sure you have such an application before wasting time on this. Usually bottle necks for web applications are in the Database. Do you have the right indexes? Is your db properly configured? Could your SQL be made more efficient? But as always benchmark, benchmark, benchmark. Otherwise you're just shooting in the dark in a very large room. -- Michael Peters Developer Plus Three, LP --------------------------------------------------------------------- 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]
