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

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12808815#comment-12808815 ] 

RH Bugzilla Integration commented on JBRULES-3699:
--------------------------------------------------

Mario Fusco <mfusco at redhat.com> made a comment on [bug 958387|https://bugzilla.redhat.com/show_bug.cgi?id=958387]

As evidenced by Toshiya the biggest part of this memory occupation is caused by the conversion of InputStreams to Strings. Unfortunately I don't think this is avoidable. Moreover there are many ways to perform this conversion, but as for example reported here:

http://www.journaldev.com/706/how-to-convert-inputstream-to-string-in-java

we are apparently already using the most memory efficient one.

I can't find a way a to improve this issue but any other suggestion is welcome.
                
> 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