[rules-users] Significant memory degradation in high transaction system

[Michael Finger]

Have you profiled your application yet? You can get a free trial of yourKit,
or play with the visual JVM in JDK 6..



sburrows wrote:
> 
> Hello,
>   After the introduction of drools into our application, we see our memory
> declining over the course of 2-3 days to the point were the garbage
> collector thrashes, latency becomes unbearable (> 5 sec) and we have to
> restart the servers.  We also notice that the garbage collector runs much
> more frequently all of the time.
> 
>   Here's our setup:
>   - drools 4.0.7 
>   - multi-threaded web application that receives around 10 hits per second
>   - about 30 rules defined
>   - we update a global RuleBase nightly by creating a new RuleBase and
> replacing the old one, so the old one should be GC'd when there are no
> more sessions using it
>   - we create a new StatefulSession for each web application session and
> call dispose() when the web session expires (30min)
>   - servers have 2GB RAM each
> 
> Besides the RuleBase reference to StatefulSession (which is removed by
> dispose), are there any other 'hooks' which might cause memory to be
> retained longer than the StatefulSession?  Is our usage correct? Has
> anyone else had this problem?  Any other ideas how to resolve this?
> 
> Thanks for your help!
> sburrows.
> 
> 

-- 
View this message in context: http://www.nabble.com/Significant-memory-degradation-in-high-transaction-system-tp22851614p22871403.html
Sent from the drools - user mailing list archive at Nabble.com.