Closed GoogleCodeExporter closed 9 years ago
Upon investigation, the engine is not running out of heap due to the number of
elements; rather, most likely the complexity of the rules being used to
generate the elements. In the current Ticket2.0 implementation, the limit seems
to be around 3500 elements with a 384 MB heap.
Note that more heap is available if inference is done separately from code
generation.
r2457: replaced 'update' and 'init' CompositeOperations.
There was a saving of 11.5% elements generated.
r2459: replaced 'fieldValue is set' CompositeCondition.
There was an additional saving of 14.5% elements generated.
Original comment by soundasleep
on 9 Jul 2010 at 5:59
Original issue reported on code.google.com by
soundasleep
on 9 Jul 2010 at 3:52