As far as I know (and I've really looked for this answer in the ActiveState documentation) IIS/Perlscript will not cache any of global data or pre-compiled scripts. Every time you invoke a page it gets compiled and executed again and there's no way to get around this other than resorting to PerlEx, which comes with it's share of obscurities (I, for instance, was unable to make it stop generating http headers in the ASP like embedded perl option, which prevented me from sending cookies, which is an important lack, and PerlEx comes with no source). The fact that you can't cache globals under IIS/Perlscript is what prevents you from keeping connections alive. Given this I believe that AgentM's is not a real solution to the problem. runrig's suggestion, which relies on a perl wrapper around microsoft persistant objects, seems like the way to go for me. If your DB tables are small enough, and most of your traffic is read only, I could suggest you putting your tables into hashes and freezing them into the Application object, which is a horrible hack, but can be a lot faster than querying the database. You can see a discussion on this at this node.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
