[rules-users] Significant memory degradation in high transaction system
Michael Finger
mfinger at overstock.com
Fri Apr 3 13:23:25 EDT 2009
Hmm. Are you using server side sessions?
sburrows wrote:
>
> Unless the leak is somewhere else. But, in general I agree, we haven't
> found any leaks so far. Nevertheless, before the release our free-memory
> never dipped below 500MB and recovered to 1.6GB during periods of low
> activity. Now, within 2-3 days (more quickly during heavier loads) our
> memory declines to near 0 and the GC thrashes. The big question is, WHY?
> If there are no memory leaks, there must be some other reason memory is
> being held.
>
> sburrows
>
>
> Michael Finger wrote:
>>
>> So your app isn't leaking memory?, the GC is just taking longer, or are
>> you running out of heap space due to a memory leak, etc. and requiring
>> more GC runs? How do you heap sizes, etc. look over time. What objects
>> are occupying the most memory?
>>
>>
>> Also, while I'm thinking about it, it seems like it would be best
>> practice to put the stateful session release in a try - finally block as
>> a best practice? ( I haven't seen this in the docs/code samples)
>>
>>
>> Mike
>>
>
>
--
View this message in context: http://www.nabble.com/Significant-memory-degradation-in-high-transaction-system-tp22851614p22872968.html
Sent from the drools - user mailing list archive at Nabble.com.
More information about the rules-users
mailing list