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

Hello: I see this is marked as fixed in https://issues.jboss.org/browse/JBRULES-2756 https://issues.jboss.org/browse/JBRULES-2756 , but I am still experiencing high CPU usage with version 5.2.0.M1. Anyone still seeing this? This is my first attempt at using Fusion, so I could be doing something wrong. I am not sure about the approach of calling fireAllRules on a timer v.s. the continuous fireUntilHalt. I think I need to keep the session in fire mode all the time to properly catch all events and allow for time sensitive rules to fire, but I don't have the luxury of keeping one of the CPUs at near 100% all the time. Since I am new to CEP, I am not sure what happens to time-window rules in the case of periodically calling fireAllRules. What happens to events inserted into entry-points when the session is not in firing mode? TIA, Alex -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Starting-engine-using... Sent from the Drools - User mailing list archive at Nabble.com.