[
https://issues.jboss.org/browse/DROOLS-1016?page=com.atlassian.jira.plugi...
]
Mario Fusco resolved DROOLS-1016.
---------------------------------
Resolution: Rejected
The increased requirement in term of the occupied permgen space is not caused by the new
phreak algorithm, but mainly by the fact that in drools 6 constraints are jitted, i.e.
converted in bytecode and then evaluated in compiled mode instead of keep using mvel for
each evaluation. You can have finer grained control over the permgen space used by drools
setting the "drools.permgenThreshold" system property. This property represents
the threshold of PermGen usage (in percentage) above which the engine stops JITting
constraints and let them run in interpreted mode. In particular setting this property to 0
will completely turn off this optimization, but I don't suggest you to do so because
the performance gain derived from evaluating the constraints in compiled mode is really
relevant. My suggestion, at least on the long term, is to migrate to JDK 8 that no longer
has a PermGen space separated from the normal heap space.
Too much memory consumption while running code on drools6.
----------------------------------------------------------
Key: DROOLS-1016
URL:
https://issues.jboss.org/browse/DROOLS-1016
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.2.0.Final
Reporter: Vivek Hingorani
Assignee: Mario Fusco
The memory usage on drools6 is far more then drools 5. Can we run the drools6 code with
Rete algorithm?
We recently migrated our project from Drools 5.3.0.Final version to Drools 6.2.0.Final
version. In production we can see a significant increase in the memory consumption per
node. we are using java 1.7. We increased the permgen space as well for drools6 from 0.5
GB to 1 GB but still the increase is too much. Is there any solution for the same.
Drools5 memory usage was 0.5GB per node with 0.5GB permgen space
Drools6 memory usage is 1.3GB per node with 1GB permgen space.
Node here is a jvm as we are using oracle coherence.
If further details are needed , let me know.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)