Hi,
Is there a way, (best practice, procedure) to evaluate how much memory
will the RuleEngine require? It must not be very precise, but it should
show at least the magnitude order.
Thank you in advance,
Ahmed.
To unsubscribe,
I think Ahmed Mohombe wrote:
Hi,
Is there a way, (best practice, procedure) to evaluate how much memory
will the RuleEngine require? It must not be very precise, but it should
show at least the magnitude order.
This is something like asking about the memory consumption of an
arbitrary
Something that I've found that works for long (time wise, that is)
problems is to just physically watch memory. On "some" Unix systems
you can watch memory load, CPU load, etc., etc. as it is happening
since it uses some low level routines and presents them graphically. I
know that you can on
Hi All,
I just wanted to squash my previous query about adding a native, general
purpose, tree storage mechanism to Jess. It's not needed -- Jess's
flexibility lets you build pretty much anything you want.
For example, I successfully tried:
a) Cross-linking facts containing Jess multislots