Yes, compiling from source is fun and you can often gain a better performance if you do it right. Actually, my system currently runs at about 50% load, so a few extra percent of performance are not absolutely necessary (but a 10x slowdown would not work). So your suggestions, which might be reasonable for your many workstations, would be out of scale in my case.

Also, no nightly runs of yum, just set up iptables and only allow ssh + http. If there is a security problem with one of these, it will make big tech news and I fix my server easily. Even if it is down for a few days, I will not loose thousands of dollars, so this is a small and acceptable risk.

In reply to Re^4: DBI/DB2 slow on Fedora, fast on SUSE by hrr
in thread DBI/DB2 slow on Fedora, fast on SUSE by hrr

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.