Mario Fusco wrote > > Yes, of course it will be possible, even if my suggestion is to avoid this > in production otherwise you will have ALL the constraints running in > interpreted mode. Actually you could already achieve this if you can > rebuild drools from the sources (you already did it, so I assume it won't > be a problem). If you want to try open the class MvelConstraint and modify > the constant JIT_THRESOLD. That constant defines after how many times a > constraint can be evaluated in interpreted mode before to get JITted, so > if you set it to a very high value (e.g. Integer.MAX_VALUE) you should be > able to completely avoid any JITting. Let me know if this works. > > I hope this helps, > Mario >
I just tested it with JIT_THRESOLD=Integer.MAX_VALUE and it effectively does wonders for both perm gen consumption (as classes no longer held by the executor thread) and - believe it or not - even performances in some cases :-) It would be great to have this configurable (either this or your other option which will limit the amount of memory used by Jitting) -- View this message in context: http://drools.46999.n3.nabble.com/Migrating-from-4-0-7-to-5-4-0-Final-tp4018215p4018481.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users