Rich Scheuerle (JIRA) wrote:
Attachment Perf Improvement ---------------------------
Key: AXIS2-2946 URL: https://issues.apache.org/jira/browse/AXIS2-2946
Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel
Reporter: Rich Scheuerle Assignee: Rich Scheuerle
I am working on a performance improvement improvement reading
attachments.
Currently the Axiom Attachments code reads bytes until it surpasses the
file threshold. If the file threshold is high (i.e. 100M) this causes
a very large buffer to be created....even if the attachment is stored
on file.
Isn't this user config error?
The improvement is to use the content-length of the message as a
heuristic to determine if the attachments should be flushed to file.
This improves performance and memory footprint.
In most cases with attachments the messages will be chunked. There's no
content length available in such cases to make the test up front on
whether to write to a file or not. Sending a 100M or even 10M attachment
without HTTP chunking is simply terrible form IMO.
Anyway if that's the edge case that you want to handle I'm fine with it. I
assume this'll go in post 1.3 due to changes to kernel APIs.
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
