Menu
▾
▴
Re: [ebxmlms-general] Turbocharging Hermes 1 with Apache AXIS (SAAJ / JAXM) performance
|
From: David RR W. \(XML\) <da...@dr...> - 2006-07-28 21:05:04
|
<div>Final footnote on this - words of caution to the wise!</div> <div> </div> <div>Turns out that the performance issue in our code related to the use of </div> <div>transient request variables in the thread calls to sendMsg.</div> <div> </div> <div>AVOID doing this! </div> <div> </div> <div>Because Hermes uses a transient variable in the send and write thread </div> <div>tracking itself - adding transient variables in other objects causes the JVM </div> <div>to have resource locking issues that prevent the send thread completing.</div> <div> </div> <div>Of course something as simple as declaring a variable proved extremely</div> <div>difficult to track down in the first place - so hopefully we can save</div> <div>others future pain in this area!</div> <div> </div> <div>Thanks, DW<BR></div> <DIV id=wmMessageComp name="wmMessageComp"><BR><BR> <BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid">-------- Original Message --------<BR>Subject: Re: [ebxmlms-general] Turbocharging Hermes 1 with Apache AXIS<BR>(SAAJ / JAXM) performance<BR>From: "David RR Webber (XML)" <da...@dr...><BR>Date: Fri, July 21, 2006 12:10 pm<BR>To: ebx...@li...<BR>Cc: Vladimir Alexovic <vla...@we...>, Ladislav Urban<BR><lad...@we...>, "David (NIH/OD) Webber"<BR><we...@od...><BR><BR> <DIV>Team,</DIV> <DIV> </DIV> <DIV>I'm just reporting back here on our findings.</DIV> <DIV> </DIV> <DIV>First Hermes 1 is now confirmed to perform at the same level as Hermes 2 - actually better - because it has a smaller memory footprint currently.</DIV> <DIV> </DIV> <DIV>We have successfully sent 130MB payloads Hermes 1 <-> Hermes 1 and the transfers take less than 1 minute - so 130MB in under 1 minute is excellent performance!</DIV> <DIV> </DIV> <DIV>The caveat is that you do need a machine with enough DRAM installed to support large payload sending - and to allocate extended memory to the java environment.</DIV> <DIV> </DIV> <DIV>We have also successfully upgraded Hermes 1 to use the latest SAAJ JAXM libraries too.</DIV> <DIV> </DIV> <DIV>So overall the outcomes on all this are positive. What we did discover was that the delay in sending was caused by our own internal code - we are in the process of re-factoring that code to resolve the issue.</DIV> <DIV> </DIV> <DIV>Anyway - just wanted to let everyone know on Hermes 1 performance - being at least as good as web service WSDL send and receive for large payloads.</DIV> <DIV> </DIV> <DIV>Thanks for all the support and help in investigating this and the successful outcome.</DIV> <DIV> </DIV> <DIV>DW<BR></DIV> <DIV id=wmMessageComp name="wmMessageComp"><BR><BR> <BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid">-------- Original Message --------<BR>Subject: [ebxmlms-general] Turbocharging Hermes 1 with Apache AXIS<BR>From: "David RR Webber (XML)" <da...@dr...><BR>Date: Thu, March 30, 2006 1:45 pm<BR>To: ebx...@li...<BR>Cc: "David (NIH/OD) Webber" <we...@od...>, ebxmlms-general<BR><ebx...@li...>, Vladimir Alexovic<BR><vla...@we...>, Ladislav Urban<BR><lad...@we...><BR><BR> <DIV>Team,</DIV> <DIV> </DIV> <DIV>Based on our benchmarking using the Hermes 2 loopback test - it appears that for large payload the AXIS based httpSend is 10x faster than the current Hermes 1 JAXM based httpSend.</DIV> <DIV> </DIV> <DIV>A 15Mbyte payload took less than 2 minutes to transfer - whereas with Hermes 1 this would take upwards of 15 to 20 minutes.</DIV> <DIV> </DIV> <DIV>The question therefore arises - looking at the Hermes 1 delivery code - it uses httpSend() class.</DIV> <DIV> </DIV> <DIV>Since this seems to do a complete hand-off to JAXM (which uses the slow sendmail based MIME) and simply return at that point - how feasible is it to create a wrapper method - that would instead use the AXIS send function as a plug-in replacement?</DIV> <DIV> </DIV> <DIV>Doing this would allow Hermes 1 and Hermes 2 to both use AXIS as the SOAP messaging layer - and obviously also give a 10x performance boost to Hermes 1.</DIV> <DIV> </DIV> <DIV>Can anyone who has worked with AXIS suggest if this is indeed feasible (obviously Hermes 2 is the example).</DIV> <DIV> </DIV> <DIV>Thoughts?</DIV> <DIV> </DIV> <DIV>DW</DIV>------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general </BLOCKQUOTE></DIV> <HR> -------------------------------------------------------------------------<BR>Take Surveys. Earn Cash. Influence the Future of IT<BR>Join SourceForge.net's Techsay panel and you'll get the chance to share your<BR>opinions on IT & business topics through brief surveys -- and earn cash<BR>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV <HR> _______________________________________________<BR>ebxmlms-general mailing list<BR>ebx...@li...<BR>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general </BLOCKQUOTE></DIV> |
