No such thing as a small change | |
PerlMonks |
Re: PERL/CGI Performanceby Ryszard (Priest) |
on Jul 30, 2002 at 08:25 UTC ( [id://186151]=note: print w/replies, xml ) | Need Help?? |
The performance of your site isnt *only* related to perl. We're talking network latency, machine speed, ram, IO, disk speed et al. Much of the overhead with perl CGI's is related to brining up the perl interpreter. (one instance per CGI). Check out mod_perl, it is apache with the perl binary build into it at compile time (Only have to load perl when you start apache).
DONT USE FLAT FILES!, I'm thinking of several reasons: Why use perl over ASP? Microsoft.. :-) completly irrational argument. TBH both may do the job, both platforms have quirks and the performance is highly dependant on application design. I'd choose perl as its easy, lots of support (you posted the question here didnt you?), and portable, (you can run it on solaris, linux, windows...). Also means your choice of host provider is not as limited. What makes MySQL better than others? Not much IMO. The latest stable release doesnt support transactions (Postgres, Oracle does). Both Postgres and MySQL are free, both have heaps of support... If youre leaning toward more of an "Enterprise" solution, Postgres may be the way to go as it is transaction based. If you're not particularly worried about this feature, MySQL might be the way to go. Of course if you have lots of cash, i'd say Oracle, which would probably be complete overkill for a small(ish) application.. :-) Anyways, good luck. Update: Whoops, i stand corrected on my ASP comments after reading IlyaM's post.
In Section
Seekers of Perl Wisdom
|
|