Greetings. We are seeing a huge slowdown in jBPM throughput when the JBPM_LOG file gets very large.
For example, during our benchmark testing we start with a "virgin" database. After three weeks of testing, we see a ~40% increase in workflow execution time. At this point, the JBPM_LOG table has about 6M (yes, million) records. If we clean the database tables, performance returns to its original level. I don't really understand why the size of JBPM_LOG has such a profound effect on performance. In production we need the log records to construct an audit trail, so disabling logging is not an option. Any suggestions on improving performance with large JBPM tables? Anyone running a high volume jBPM application care to comment on performance over time? BTW, this is jBPM 3.1.2 with selected fixes from later versions applied. Thanx. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213536#4213536 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213536 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
