I've done extensive load-testing with Attachments.. and it seems to work beautifully! The best thing about the Attachments as regards performance is that the message is entirely outside the SOAP envelope.. This allows the Axis engine to process the SOAP Headers without having to read in the entire 1 GIG of business data.. The AXIS engine thus processes is very quickly.. And passes on the 1Gig of data to the business logic.. In all our testing, the Axis engine was less than 3-5% of the total transaction time.. And it handled all requests without any errors! The errors starting showing up in the business logic layer when we had simulataneous users of 500. But not the axis layer..
I've published some of those numbers at: http://www.informit.com/articles/article.asp?p=177376 You can get the article without advertisements at: http://www.informit.com/articles/printerfriendly.asp?p=177376 -- Rajal -----Original Message----- From: Tim Dev [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 12:08 PM To: [EMAIL PROTECTED] Subject: attachments I am thinking of using attachments, but I have a few questions: 1) Given that the attachment sizes will be from 2KB to maybe 1GB or even more, can Axis deal with them in a performant way? 2) I have the option of retrieving/sending content via a plain HTTP servlet using GET/PUT and I could make it look like it's part of the same session because the two servlets run in the same webapp and I can set the same session cookie for both the WS requests and the HTTP requests. I know the plain HTTP servlet performs as best as it can, should I use this instead of going thru the trouble of setting up attachments and running into perfromance issues with Axis? 3) Do I need to enable the "streaming" mode for my Axis service in order to use attachments or make them perform well (I would not like a 1GB attachment to be cached in memory ...) 4) For interop with .NET, I understand .NET only supports DIME and not MIME. How difficult is it to get both to perform in Axis? Thanks. Tim
