Hi Ernest, Thank you very much for addressing my concerns. The time consumed for the compilation of rules (as you pointed out) is not a primary concern for our applications. I did realize that that phase would only occupy startup time, and for a long running system, is not the most relevant metric to be concerned with. There is however, an exception to this case where data is influencing the creation of new rules which may subsequently be inserted into the Rete engine at runtime. I doubt however that 10,000 rules would be inserted into the engine dynamically - and even so, at 5 or so secs. per 10K the engine's performance would not be a hinderance at all.
Since I have your attention :) - I would like to share with you my primary use case - and the situation for which I am considering Jess. I am highly motivated to show Jess's applicability to my company due to the availability of "Fuzzy Rules" for Jess, for use in a highly transactional financial application with conceivably large data throughput. "Fuzzy Rules" being almost exclusively available in Jess, makes it a high priority. Any input or guidance you could share with me on this point would be highly appreciated - if you find that there are hints or insights that may become important in our usage or determination of Jess as an option? Once again, thanks David -------------------------------------------------------------------- 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]. --------------------------------------------------------------------
