Greetings. We've discovered what might be an indication that Jess 4.3
is suffering from the "unintentional object retention syndrome",
i.e. a memory leak. Some clarification would be appreciated.
Profiling our application with OptimizeIt (Intuitive Systems), we've
noticed that instance counts of class 'jess.TokenTree' increase
"without bounds"; allow other instance counts remain normal for our
system. As an example, during a recent one-hour run, the instance
count for 'jess.TokenTree' exceeded 47K, during which time the
inference engine was running much of the time. In comparison, counts
for class String, which are created with abandon, consistently hovered
around 7K (I don't know if this comparison means anything; I just
threw it in there). Other Jess classes seem to maintain reasonable
instance counts.
As background, we're using Jess for an embedded expert system within a
long-running simulation program, with the JavaSoft reference VM
(1.1.6) on Solaris 2.6. I appreciate your comments.
Regards,
--
-------------------------------------------------------------
David E. Young
Fujitsu Network Communications "The fact that ... we still
([EMAIL PROTECTED]) live well cannot ease the pain of
feeling that we no longer live nobly."
-- John Updike
"Programming should be fun,
programs should be beautiful"
-- P. Graham
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
