[rules-users] Multi-threading inefficiency caused by static class synchronization?

ping jinpingv at hotmail.com
Tue Dec 11 13:20:43 EST 2012


Thank you. You are right the locks are guarding the session creation.
I will try stateful session with fact retracting.
I was using stateless session because the rules I'm going to deploy are all
simple rules without much inference.
So another question is: to make the multi-threading efficient, I need to
reuse the stateful session. In that case, will the memory be a problem if I
keep the session running too long without dispose it? Or I need to create a
new session once every hour or day? Or maybe retracting the facts will keep
the memory footprint low?

-Ping



--
View this message in context: http://drools.46999.n3.nabble.com/Multi-threading-inefficiency-caused-by-static-class-synchronization-tp4021160p4021170.html
Sent from the Drools: User forum mailing list archive at Nabble.com.


More information about the rules-users mailing list