in reply to [untitled node, ID 195604]
You don't say but I'm assuming you are running your Perl application via CGI, in which case the server is having to fork off a copy of Perl everytime a page is viewed, then close it down once it's finished with it. Unless you have thought of caching this is for EVERY page view, too. This uses up loads of memory & CPU and is a good way to make you unpopular with the system admin team.
Popular web sites that use Perl a lot, use mod_Perl, which starts the Perl code once when the server starts, and keeps it in memory. This means that a fresh copy of Perl is not started up for every page view.
Chances are you won't have access to mod_Perl, so you sys admin has suggested PHP instead, as they probably have PHP configured for use.
See also: Perl/CGI Performance for a Shopping Cart
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
195616
by Samn (Monk) on Sep 06, 2002 at 12:01 UTC | |
by ajt (Prior) on Sep 06, 2002 at 12:32 UTC | |
by RMGir (Prior) on Sep 06, 2002 at 12:28 UTC |