<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Amit Mhatre wrote:
<blockquote
cite="mid:fad06c9b0808102115k12cd9a2bva40a6026a820a8e7@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,<br>
this might either be a java-users questions or a drools-users, but I'd
like to try here to see if somebody has any suggestions for me.<br>
<br>
I have observed that the ruleFlow that I am using gets slower and
slower since its initial deployment. It initially started taking like
30mins to evaluate all the rules, but the run-time goes up to about
4hours in about 4 days.<br>
<br>
I am using a statelessSession. I do a RuleBaseFactory().newRuleBase()
and ruleBase.newStatelessSession() each time I begin an evaluation (I
evaluate about 50k objects, once a day). I have the ruleBase as a
private instance in an EvaluationHandler which does other evaluations
as well and is a singleton which is obtained from a factory.<br>
<br>
Has anyone else too on this forum faced this issue? I found this
archive, but no reply to it: <a moz-do-not-send="true"
href="http://www.nabble.com/Performance-Question-with-Stateless-Session-to14704425.html#a14704425">http://www.nabble.com/Performance-Question-with-Stateless-Session-to14704425.html#a14704425</a><br>
<br>
Could it be that a new ruleBase is being created each time I do an
evaluation (it obviously is), but a reference to the old ruleBase still
hangs around (and hence the entire WorkingMemory)? I checked the
RuleBase apis and I couldn't find anything that could help me clear the
workingMemory once I am done with evaluating all the rules.<br>
<br>
Would be great if somebody could ched some light into this issue that
I am facing and/or let me know the path I must follow to find the
root-cause of the slowing down of the evaluations.<br>
</div>
</blockquote>
Add the drools source code to your classpath and see what's going on
when it uses stateless sessions. I'd also recommend you install a free
jprofiler trial, it'll help pin point any memory leaks. When you find
it please open a jira with a test for that leak.<br>
<blockquote
cite="mid:fad06c9b0808102115k12cd9a2bva40a6026a820a8e7@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
Thanks,<br>
- am<br>
<br>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
</body>
</html>