Thanks Wolfgang- I did not realize the stateless session was just a wrapper around the stateful session. I think the stateful with manual cleanup after each fireAllRules invocation is the way to go here.
As a follow up question, do you think Drools and Rules Engines in general are the way to go for operations that distort object field values one object at a time? Would an embedded scripting language better fit this usecase? I also did some additional benchmarking with virtually the same stateful session setup. The below plot shows execution time of the rules engine for Java POJO (static) and MessagePack (Dynamic) Messages from 1000 - 200K messages in step sizes of 1000 messages. I was surprised to see the discrete jumps of 1 second in execution time. I was also surprised to see that on the low end execution time for a few thousand messages was 1 second? That seemed slow and why the discrete jumps? Sorry no label on plot: Y Axis is Exec time in seconds X Axis is Number of Messages (Step Size 1K messages) http://drools.46999.n3.nabble.com/file/n3210745/WithPayloadNoFieldRemoval.jpg Ryan R. -- View this message in context: http://drools.46999.n3.nabble.com/Stateful-vs-Stateless-Session-Performance-tp3208057p3210745.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
