[Gllug] Perl / PHP

[Richard Cottrill]

In terms of performance Perl (using mod_perl for Apache or some other
persistent Perl interpreter/cache like the ActiveState thingy for IIS) is
"quick".

Perl can be a dog if a database query returns very many rows because it
seems to do lots of malloc()s  or something and it slows right down. I'm not
sure what you're doing with your system; but in an intranet system I
wouldn't think that there would be massive queries returned to a web page
(you can't read 100MB of HTML anyway). Carefully written SQL can mitigate
the hassles of big record sets being returned.

Caveat: I used a waaaaaay less-than-optimal set-up when I was using Perl,
MySQL, and Apache so other people are likely to come up with better
clarifications and caveats.

I liked writing Perl because there were lots of evil hacks you could see;
but sanity stayed your
hand. Still, it's nice to see the hacks anyway.

I reckon Perl has legs in it. People with a preference for PHP may pepper
you with perturbed policies however.

Richard

> -----Original Message-----
> From: gllug-admin at linux.co.uk [mailto:gllug-admin at linux.co.uk]On Behalf
> Of Kristian Davies
> Sent: Thursday, May 09, 2002 4:35 PM
> To: 'gllug at linux.co.uk'
> Subject: [Gllug] Perl / PHP
>
>
> Hi All,
>
> My first post, sorry if it is slightly off topic.
>
> What difference would it make when writing an intranet system
> (inc big mysql
> database) in perl rather than using php, performance wise?
>
>
> tia,
>
> Kristian
>
> --
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug
>


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug