[rules-users] Starting engine using fireUntilHalt and inserting no facts results in 50% CPU usage

jschmied nabble at juergenschmied.de
Mon Oct 25 08:02:51 EDT 2010


You can call fireAllRules after every event changing the state of the facts
or of the ruleflow. When you do event stream processing and use the time
inside your rules, the time is a change event too. So you have to use
fireUntilHalt if you can't afford to have the small pauses using
fireAllRules/Sleep in a loop.

-- 
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Starting-engine-using-fireUntilHalt-and-inserting-no-facts-results-in-50-CPU-usage-tp1760370p1766875.html
Sent from the Drools - User mailing list archive at Nabble.com.



More information about the rules-users mailing list