Thank you for the advice. MySQL isn't an issue. We're running the db on a seperate box behind the firewall.

Actually, that's what started this current migration. The old machine used to run MySQL and the search scripts, but was getting overloaded, so we added a new dedicated db server and redeployed the old box, switching to Apache to get output compression, persistent db connections and so forth.

Interestingly, I benchmarked MySQL (4.016, I think) on FreeBSD on the new machine (dual 2.8Mhz P4s) versus Windows 2003. Who'd have thunk? On loading 2.5 million records, Windows 2003 was faster by a fair margin. The same was true for W2K as it was either about the same or slower than FreeBSD. As I recall, the reasons were largely due to hyperthreading on the P4 as W2K3 sees 2 CPUs for each processor along with other performance improvements in W2K3.

I've got the FreeBSD 4.9 install disks, so I'll give it a go. I appreciate the porting tips. We're trying to keep the code as generic as possible so that it can also run in a standard perl environment, so we should be ok there, but will take a hard look at the migration docs.

Rod

In reply to Re: Re^5: Is mod_perl for Windoze not ready for prime time? by Anonymous Monk
in thread Is mod_perl for Windoze not ready for prime time? 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.