Performance impact on Logging mode:Asyn and Sync

Hi Guys,

Need your input regarding this topic. You know there are two modes Asyn and Sync for different loggers of webMethods Integration Server 8.

We are doing a BPM project, with several Business Process Models. During the testing, we found once we changed the mode of Process Logger from Aync to Sync, then we could get better performance. But we didn’t find any words from webMethods documentation can prove it.

Do you have any thoughts on this?


I researched some WM documents and concluded as following. Could you please share your thoughts?

1, If you set the logging mode to Aync, it means all the audit logs would be wrote to a queue, and there is another IS thread will move the audit log entries from this queue to Audit database. This is so called Aync. As working in this mode, even we set the max JDBC connections to a biggger number, it is not fully utilized. I estimate the concurrent DB writing sessions might be less than 10.

2, If you set the logging mode to Sync, it means IS writes all the audit logs to Audit DB directly. So this case, IS will use all available JDBC connections to database, here is it 50. Hence, it will get better performance.

However, we have trade-off here. Under Aync mode, it writes the log entries to a queue first, so here this queue is working as a transient store, so even the IS lost the DB connection to database, the logging entries are not lost except the queue is full. Default size of this queue is 100000.
But for Sync mode, it means we may lose the audit logs if the IS lost the connectivity to audit DB.

Hi Kenny,

in the case that sync logging fails (due to lost DB connection for example) it switches to async for those entries it could not log (see webMethods Audit Logging Guide).

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.