We've been using W2K, IIS and ActiveState perl for a number of years. That's worked well for us generally, but the number of concurrent processors and multiple db connections is now causing periodic problems. So we've planning to go to Apache and mod_perl or fast_cgi to get persistent db connections and avoid the multiple perl processes as well as knock up the performance. This effort will require a fair amount of work as there is tons of code and it'll all need to be reviewed and much of it modified to work right in a persistent environment.

The server is a dual CPU machine that will likely by running Win2003. Given that starting point which packages would you choose to use? Performance in a high volume production environment is a primary consideration along with stability. Ease of porting old code is also important.

I've been seeing some information about Indigoperl. What are the pros and cons versus ActiveState?

My impression from a few articles is that the current mod_perl doesn't handle multiple processors in Windows but that 2.0 does, but isn't fully stable? Is fast_cgi a better alternative for a dual CPU Windows machine or is my impression wrong?

Finally, is one DBI package better than another? We've been using whatever is linked from the mySQL site currently.

Thanks

In reply to Best perl environment for mySQL server? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.