One rather useful piece of information you didn't include is what O/S you are currently using throughout the company (I'm making the assumption that the company is more than a few people). Unless there are significant problems with it, I would vote for using the same O/S on the production server. If you are doing it as part of a turn-key system for a customer, I would ask a similar question: what O/S do you typically use, and why not use the same one here?

All three are sufficiently reliable and secure for production use; all three are probably roughly equal in overall performance until specialized hardware starts coming into play (in which case, Sun will probably win; earlier versions of Solaris scaled pretty much linearly to several thousand processors)unless the company is severely cash-strapped, the initial purchase cost for software and hardware should not be a major factor. Support costs will be, which is why (I'm repeating myself) the O/S currently being used should be given first preference.

I've got a soft spot for FreeBSD, mostly because of how long it managed to hang on at Hotmail after Hotmail became a Microsoft property.

emc

</code>

In reply to Re: Solaris 10, FreeBSD or RHE Linux for production server Perl box? by swampyankee
in thread Solaris 10, FreeBSD or RHE Linux for production server Perl box? 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.