Speeding up logging by caching is all great until you need your log to find/trace a mysterious application crash - and the most recent 100 entries in the log were lost in the crash.

If you can find a way to isolate your logging from the application far enough that a crash doesn't impact it, like writing your own logging daemon or using syslog or whatever, I would look at using that approach.

If you don't really deal with application crashes since the logs are more for application auditing and the application itself is usually stable, then caching things before writing it to disk might be a viable approach.

Personally, I would look at the pragmata that SQLite itself offers, for example pragma synchronous=off, which gives up some of the durability for improved performance.

In reply to Re: Log::Log4perl::Appender::DBI and SQLite by Corion
in thread Log::Log4perl::Appender::DBI and SQLite by clueless newbie

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.