[rules-users] Best practice to use heap memory effectively

[Wolfgang Laun]

This post and the previous one are rather confusing.

Processing 1M facts per day should not be a problem when you don't
need to keep them in WM for combined evaluations.

session.dispose() is used to clean up after a session isn't required any
more; if you don't do that you'll run into memory problems.

You don't have a "memory leak" if you just create objects (and insert them
into WM) without removing them (retract them from WM).

It's unclear to me why you can't simply retract a fact after it has been
evaluated; there's no indication in your post what needs to be done
with these events/facts. It is, however, rather improbable that you'll
need to create a new session for each and every fact.

-W


On 01/11/2012, mohan <mohan.narangoda at gmail.com> wrote:
> Hi folks,
> Still i'm struggling to solve memory issue. My application will hang up
> after one day due to memory leak. I’m not calling session.dispose() and
> think it was the main reason behind this. How can I keep events & accumulate
> number of events inside WM in a particular day without a single static
> StatefulKnowledgeSession?
>
> With kind regards,
> Mohan
>
>
>
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effectively-tp4020194p4020646.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
>
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>