I would be interested to hear the time measurements of such inserting into a stateless session.
The alternative is obviously holding a statefull session, and continuously updating it with new facts. The cons of this is performance... A painful issue. On Tue, Nov 18, 2008 at 6:15 PM, techy <[EMAIL PROTECTED]> wrote: > > I take back.. I noticed that it happened while I was doing memory profiling. > for normal execution, it works fine.. > > Is there any limit on # of facts to be inserted into stateless session? or > does it depend only on heap size? > thanks. > > > techy wrote: >> >> If I have set of rules(say 5 rules for now.. which just compares few >> fields in facts and increments execution count on Rule Object as a >> consequence) working on single fact and I have huge amount of data to >> process, >> How many maximum facts can I insert into stateless session at a time for >> faster execution of rules for each execution? >> >> I inserted to 50,000 facts into stateless session(desktop runs in win XP, >> and assigned 500MB head size to the java process) and with drools debug >> enabled, I noticed that insertion itself takes(>10 secs) considerable >> time. >> >> I would like to know best practices in such situations. appreciate your >> help. >> >> Thanks! >> > > -- > View this message in context: > http://www.nabble.com/drools-performance-%3A-max-limit-on---of-facts-for-each-execution-tp20562112p20562748.html > Sent from the drools - user mailing list archive at Nabble.com. > > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > -- Cheers, Maxim Veksler "Free as in Freedom" - Do u GNU ? _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
