For the most part, there shouldn't be any significant performance
implications. If there are many simultaneous threads the throughput
might be greater if you use runUntilHalt() because there will be less
contention. I would do whichever makes the design cleaner for you.
On Jan 9, 2007, at 2:50 PM, Skeptic 2000 wrote:
Hi,
I have some java code that create ShadowFact and some rules that
modify them at creation and when they are modified on the Java side.
I'm trying to compare two way of doing this :
First, doing a engine.runUntilHalt() and doing my java code that
handle the shadowfact after.
Second, after each manipulation on the Java side, doing a engine.run
().
On performance side, what is the difference between the two ?
You can probably guess that I want to do this because I need to be
sure that Jess has runned out before doing some extra Java code. I
don't want to go in details here of why I need this behavior, but
I'm pretty sure that it don't go agains't the Jess spirit.
Thanks
Soyez parmi les premiers à essayer Windows Live Mail.
---------------------------------------------------------
Ernest Friedman-Hill
Advanced Software Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 294-2234
PO Box 969, MS 9012 [EMAIL PROTECTED]
Livermore, CA 94550 http://www.jessrules.com
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
