Since noone else seems to have any information on this, I can tell you what I heard from a guy working for telco company with a rather huge number of transactions.

They did _not_ get acceptable performance and ended up logging insert-statements via FileAppender and PatternLayout, and then batch-inserting these on regular intervals.

A more manual solution, of course, but a guarantee that db performance will not influence critical production performance. Anyway, I guess db performance will rely mostly on non-log4j related parameters like networking, db configuration etc.

Just wanted to let you know :)

- Thomas S.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to