You don't think those numbers look bad? If I was shopping on Amazon and it took 11 to 25 seconds to check out, I would be worried. If you look at some of the newer apps like Jira, you have sub second response times when saving entries (creating or updating).
I designed an interface to retrieve (read only) using Oracle XMLGEN, a J2EE component (retrieve data from Oracle and output to application/xml output stream) and XSL. It was able to render an issue with interactions, show related items, work logs, etc. with sub second page load times. This is where web applications should be. There are a number of things you can do to get some quick performance gains with web servers: - Enable compression on your web server (Apache mod_deflate) - Set up the cache parameters more realistically (images, css, etc., set reasonable expiration periods) - Make sure the connection between your J2EE container and web server is optimized - Make sure your web service calls are optimized Apache JMeter is a great free too for load testing your web applications. You can simulate a large number of users, define ramp up and ramp down periods, among a number of other things. Have you tried other web service offerings, like JSS XML Gateway? On Tue, Sep 20, 2011 at 6:58 PM, Robert Molenda <[email protected]>wrote: > ** I've asked BMC for some references, white papers, etc about the > following scenario - and have not received much of a response as of yet, so > I'll ask the people that know :) > > I have a customer that has created a 'web content' (read presentation layer > / portal) that allows them to create, query and update incidents. This > portal simply consumes the Web Services for doing this. While this is quite > functional - they do have some performance concerns - while the times they > are experiencing are 'acceptable' - they feel they can be improved, and thus > have reached out to see what we can find out. > > So, does anyone else have created their own portal, and have utilized Web > Services, or native Java API, etc..?? What are your experiences, etc?? Are > there any pros/cons of web-services over java api? > > Next - does anyone have any performance statistics they can share with > regards to Incident Create, Incident Query and Incident Modify web-services? > > To be fare with my fellow friends here - below are some of the numbers the > customer is currently experiencing... > > The system(s) are well tuned and architected, load balanced and separated > traffic across segments, it is ARS7.5 and Oracle for your reference... > > Search Incident - 4.7 Sec (see results list) > View Incident - 10.9 Sec > Update Incident without attachment - 11.5 Sec > Submit Incident without attachment - 20.4 Sec > Submit Incident with 3MB attachment - 25.4 Sec > > So honestly - these numbers do not appear all that bad - but they are > asking for comparisons - so I figured I'd ask :) > > Thanks - and hope everyone is have a great time at RUG (wish I could have > attended this year to ask this question in person) > > Robert Molenda > [email protected] > > > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
