I tried already to start it nice (e.g. reniced after i noticed) it, it wont help much it is very "consuming" anyway.

Then you're either a.) on a crap operating system or b.) not CPU-bound. I'd guess b.), especially with sa-learn and a huge bayesian database it's quite likely that you're either running out of RAM (and thus starting to swap) or just using up all the systems IO. Try doing a system call trace on the process (strace on Linux), also see what your general resource usage ist (vmstat). Stopping and restarting the process is an extremely crude tool and likely to do more harm and good IMO (especially since AFAICR sa-learn actually locks the bayesian database while inserting, which means spamassassin has to wait for the process to restart if you stop and start when the lock is being held).


All dogma is stupid.

In reply to Re^3: Performance issues by tirwhan
in thread Performance issues by matze77

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.