Bug 882155 - Large memory allocation per request in drools-camel-server
Summary: Large memory allocation per request in drools-camel-server
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: QE, unspecified
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: trev
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-30 09:55 UTC by Toshiya Kobayashi
Modified: 2020-04-27 01:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 958387 (view as bug list)
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
JBoss_Benchmark_Request.xml (194.69 KB, text/xml)
2012-11-30 09:57 UTC, Toshiya Kobayashi
no flags Details
numbers.drl (748.70 KB, application/octet-stream)
2012-11-30 09:58 UTC, Toshiya Kobayashi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBRULES-3699 0 Major Open Large memory allocation per request in drools-camel-server 2014-09-05 01:01:31 UTC

Description Toshiya Kobayashi 2012-11-30 09:55:17 UTC
Description of problem:

In drools-camel-server, memory allocation during request/response message handling is quite larger than actual request/response size.

For example, with attached numbers.drl and JBoss_Benchmark_Request.xml, one SOAP request results in 45MB+ object allocation while the actual request size is 200KB and the response size is 650KB. They are short-lived objects so wouldn't be a memory leak but affect performance especially under high load.

Comment 1 Toshiya Kobayashi 2012-11-30 09:57:43 UTC
Created attachment 654913 [details]
JBoss_Benchmark_Request.xml

Comment 2 Toshiya Kobayashi 2012-11-30 09:58:24 UTC
Created attachment 654914 [details]
numbers.drl


Note You need to log in before you can comment on or make changes to this bug.