[jboss-jira] [JBoss JIRA] (JBRULES-3699) Large memory allocation per request in drools-camel-server

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Wed May 1 05:42:53 EDT 2013


     [ https://issues.jboss.org/browse/JBRULES-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated JBRULES-3699:
---------------------------------------------

    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=882155, https://bugzilla.redhat.com/show_bug.cgi?id=958387  (was: https://bugzilla.redhat.com/show_bug.cgi?id=882155)

    
> Large memory allocation per request in drools-camel-server
> ----------------------------------------------------------
>
>                 Key: JBRULES-3699
>                 URL: https://issues.jboss.org/browse/JBRULES-3699
>             Project: JBRULES
>          Issue Type: Quality Risk
>      Security Level: Public(Everyone can see) 
>          Components: drools-camel
>    Affects Versions: 5.4.0.Final
>            Reporter: Toshiya Kobayashi
>            Assignee: Mark Proctor
>         Attachments: JBoss_Benchmark_Request.xml, numbers.drl
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list