Thanks to all the help I have received from this mailing list, especailly from Ernest, my ruleset is working and passing all the tests that have been thrown at it. Thanks for the assistance. This is very good news, but it also means performance testing is the next step. Initial runs are promising (especailly after turning off watch-all :P ) however it looks like we need to squeze some more performance out of jess.
Does anyone have any suggestions/experiences that might help me out? So far I know that I need to reduce the number of partial matches in my ruleset (by moving the most specific guards to the top of the LHS) and move the most transient guards to the bottom of the LHS. Beyond that, what else is there to do?
Here is some information about my environment:
My ruleset is about 25 rules
Typically there are 40-50 facts in the system.
Of those 25 rules, 5 are auto focus, the rest live in their own module
It may be possible to remove the auto focus part of some of the rules with some cleverness if it would synificantly help performance
I am using jess from a web environment where many jess engines (1 per user, current load testing involves 100 users) are in operation at a time. Each time a jess engine is created my .clp files are parsed and loaded. Is it possible to somehow cache the parsed clp file so each engine doesn't need to reparse it? At the very least it would be possible to pool available jess engines that already have loaded and parsed the config files. Has anyone tried this before and seen good results?
Again, thanks for the help,
Ryan
-------------------------------------------------------------------- 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] --------------------------------------------------------------------