Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread Wolfgang Laun
Before I say something, I should know: * If an EvemetierCalculDHF accompanies an EvemetierData object: is this a 1:1 relationship or are there several EvemetierData objects tied to a single EvemetierCalculDHF? * Is EvemetierCalculDHF.evemetier a Collection? (Probably yes if the answer to the

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread ganeshneelekani
Hi, This occurs mainly when if you not executing retract() ot dispose() on particular object. If you have employee as an object , and you are doing a transition using employee object its better to use retract (employee ), which will remove or clear an object. regards Ganesh Neelekani --

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread bvoisin
Thanks for your time and answers, and sorry for the incomplete information. There is a 1:1 relationship between EvemetierCalculDHF and EvemetierData objects. The reason for the EvemetierCalculDHF is that we want the EvemetierData structure to be independent from the rules, and therefore needed a

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread bvoisin
Hi Ganesh, I'm not sure I understand your answer. My problem is on the network of Tuples that the engine creates on objects in memory. Of course, if I could retract the EvemetierData and have only a limited set the WM memory would be smaller and my problem not one any more, but currently this is

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread Wolfgang Laun
On 12/06/2014, bvoisin benoit.voi...@igc-erp.com wrote: I did not quite understand your last paragraph on a representative. Do you have an example I could study ? Given a set of facts that match some constraints, and you want to accumulate them in some way, this approach appears to achieve it:

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-12 Thread bvoisin
Thanks I understand now. It is quite clear. In my case however, the accumulated Foo's will be different for each source Foo. The two classes could have been different. A more precise sample conditions would be : $a: A(someConditions) accumulate ($b:B(someField==$a.somefield); ) My

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-11 Thread Wolfgang Laun
Most of the time, a look on a (representative) sample of the rules is enough for some watchers of this list to drop a few pointers. There are some Best Practices, but people tend to come up with new counter-examples ;-) -W On 11/06/2014, bvoisin benoit.voi...@igc-erp.com wrote: Hi all, With

Re: [rules-users] Analysing OutOfMemory, too many RightTuple

2014-06-11 Thread bvoisin
Most of the RightTuple's sinks are AccumulatorNodes. Here is one of the 80 rules that I believe cause my problem. The other 80 rules are similar, but will change in the places I formatted in /italic/. Some information on this rule: * The EvemetierData is the business class. They are 10-100k