[rules-users] Drools consuming a lot of memory for short lived objects thus impacting average response time.

[manohars]

By response time we mean - rule execution time - insert input-> Fire rule
->get the result.

We are okay with loading KnowledgeBase.
While using Decision tables, we observed a lot many short lived objects
getting created. Java Profiler pointed out the area in drools.mvel and
VariableIndexResolver packages.

We have standalone Java engine that uses RuleEngineService built on Drools.
Excel files are per-compiled into .pkg before running Java Engine.

We are using several decision tables in multiple excel rule files so there
are many more rules to be executed before reaching the result.

For many requests , response time is okay however due to too many short
lived objects, GC cycles are increased and hence it is impacting response
time for some of the requests,.. increasing overall average response time.

Any suggestions/ideas/options would be appreciated.


Thanks,
M



--
View this message in context: http://drools.46999.n3.nabble.com/Drools-consuming-a-lot-of-memory-for-short-lived-objects-thus-impacting-average-response-time-tp4020948p4020950.html
Sent from the Drools: User forum mailing list archive at Nabble.com.