You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2005/10/20 15:44:55 UTC

[jira] Resolved: (AXIS-2263) Very poor performance using Multipart attachments

     [ http://issues.apache.org/jira/browse/AXIS-2263?page=all ]
     
Davanum Srinivas resolved AXIS-2263:
------------------------------------

    Resolution: Fixed

Check Axis 1.3 it has a streaming mechanism for pulling attachments by yourself.

-- dims

> Very poor performance using Multipart attachments
> -------------------------------------------------
>
>          Key: AXIS-2263
>          URL: http://issues.apache.org/jira/browse/AXIS-2263
>      Project: Apache Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.1, 1.2
>  Environment: All
>     Reporter: dave irving

>
> Im trying to get high throughput of SOAP messages with attachments.
> MultiPartRelatedInputStream's use of ManagedMemoryDataSource is currently preventing be from achieving this.
> (See MultiPartRelatedInputStream#readTillFound).
> Currently, it appears that any attachment over 16k is getting written to disk. This causes several performance problems (cleaning up the temporary files seems to be the main one).
> Im running in an environment with a large amount of memory, and in this context the pre-emptive disk-writing currently seems to be hurting rather than helping.
> To test this, I effectively switched off disk-writing by updating the cache size to Integer.MAX_VALUE.
> My throughput shot up by an order of magnitude (1300 messages / sec from 100 messages / sec).
> Can the cache limit be made configurable?
> Or better still, we could just supply a non-persisting DataSource and have the option to configure axis to use that.
> As it stands, this will probably have a negative performance impact on any system trying to get high throughput of messages with attachments.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira