Ernest,
Have you considered implementing these things as memory-sensitive
"memories" or caches, by taking advantage of Java's Soft/WeakReference
framework? I haven't profiled Jess recently (the memory usage behavior
is basically as you describe, it grows up to a certain point and then
settles down).
In other news, we're still seeing a weird Jess bug that causes
(bind ?foo (call ...)) to sometimes return a java.lang.String object.
I know it sounds crazy but that's the only explanation, and I think
it has something to do with threading. I'm currently writing a Jess
unit test that does lots of crazy asserts/rules/funcalls from
many different threads and hopefully I can find a 100% reproducible
case. Any advice?
c
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [020627 11:43]:
> The important issue is not whether the memory usage grows, but whether
> it grows forever or levels off. It is normal for it to grow and not
> shrink; it would not be normal for it to grow forever, however. Which
> are you observing?
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
