Benchmarking will be your friend in this case. Typically you want the code around writing to the file system to be as fast as possible. "How much" of a burden the diagnostic logging will be is best determined by trying it out.
On Thu, Feb 6, 2014 at 3:10 AM, xabhi <xabh...@gmail.com> wrote: > Hi, > How much burden does kahadb diagnostic logging puts on message broker? > I want to catch filesystem issues as soon as possible and I found this > diagnostic logging option. > > Has anybody used it? Will it cause any additional burden on broker? > > Thanks, > Abhi > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Kahadb-diagnostic-logging-tp4677536.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
