Hello Ernest,
Here's where the problem lies. The one-engine/one-user architecture is
inherently inefficient. The simplest change that would improve things
would be to still use one engine per user, but as you suggest, cache
the engines with the rules loaded. A (reset) before each user would
be
I think Marcus Schlappa wrote:
To save time for building the rete network each time,
I'd like to cache the engine state with the rules already loaded as you
said before ...
1) At application startup, create a bunch of jess.Rete objects.
2) Load the rules into each one.
3) Store them in
I did that once. Long, long ago in a land far, far away. A place
called VEA at FedEx. Virtual Enterprise Architecture. A time before
J2EE. J2EE solved the problem that I had solved way back then using
the pre-alpha version of Advisor, now called Blaze Advisor. By the
time you get through with
I think Marcus Schlappa wrote:
Hello,
How can i cache the engine with the rules loaded?
Do you mean the jess-commands bload and bsave?
By engine we mean a single instance of the jess.Rete class. You can
create as many instances of this class as you wish, and load each one
with rules.
