First, have you verified the problem is not your design? For instance you
are not trying to return 10,000 rows from a database to a single page right?
Most performance problems are due to design problems.
Second, have you benchmarked your scripts to make sure they run as fast as
possible? Or to at least localize the problem?
Third, have you tuned your web server?
Finally, perhaps you need a different web server. It sounds like you are
running the interpreter for every request. Apache, with mod_perl, allows
the interpreter to run only once. And that allows your script to stay in
memory rather than starting and stopping every time.
> Behalf Of Eric Smith
>
> Hi
>
> I mailed recently on this subject but received no response :( so lets try
> again *shrugs*.
>
> I develop in perl for win32 end-users. We have chosen to deploy the perl
> as cgi scripts so user has a browser interface on the local machine
> (obviously this is scalable to internet and that is the main motivation
> for this approach).
>
> A currently unresolved drawback is /performance/ due to the follwing
> factors IMO:
> 1. compiling with perlapp to exe -major issue
> 2. Xitami webserver - possible
> 3. there are also a number of less important factors I am sure
>
> We find that these scripts when executed from the dos (or cygwin) prompt
> as .pl files run (say) 4 times faster than their .exe counterparts.
>
> Any suggestions where we may make an impact on increasing performance of
> our perl?
>
> --
> Eric Smith
> [EMAIL PROTECTED]
>
> ---
> You are currently subscribed to perl-win32-users as: [EMAIL PROTECTED]
> To unsubscribe, forward this message to
> [EMAIL PROTECTED]
> For non-automated Mailing List support, send email to
> [EMAIL PROTECTED]
>
---
You are currently subscribed to perl-win32-users as: [[email protected]]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
