[ https://issues.jboss.org/browse/DROOLS-2409?page=com.atlassian.jira.plugi... ] Srinivas ev edited comment on DROOLS-2409 at 9/18/18 9:36 AM: -------------------------------------------------------------- Hi Mario, For your comment - I have a similar case where in my application, the load may go up to 100 events per second and there will be a possibility of getting the same load for long hours. As per your statement regarding overwhelming the engine, the engine may fail to execute the rules for incoming events or eviction. What solutions I can assume for this problem. When I did the experiment last time for my project, I observed drools engine at some stage(when the number of events in drools stateful session crossed ~20 lakh) consuming all the events into it without performing any operation regarding rule evaluations/persistence timers execution( for example). I can share the reproducer in case needed. Thanks, was (Author: ev.srinivas): Hi Mario, For your comment - I have a similar case where in my application, the load may go up to 100 events per second and there will be a possibility of getting the same load for long hours. As per your statement regarding overwhelming the engine, the engine may fail to execute the rules for incoming events or eviction. What solutions I can assume for this problem. When I did the experiment last time for my project, I observed drools engine consuming all the events into it without performing any operation regarding rule evaluations/persistence timers execution( for example). I can share the reproducer in case needed. Thanks, -- This message was sent by Atlassian JIRA (v7.5.0#75005)