Terry, One major difference between pulling it up in the Mid-Tier, and pulling it back via web services is this.
Mid-Tier - Pulls the results list for ~500 entries, and pulls all fields for 1 record Web Service - Pulls ALL fields for ~500 records So, you can see how the Web Service might take a bit more time....not because of the overhead of the web service, but instead because of the sheer amount of data that's being returned via web service instead of Mid-Tier. If you move to 9.x, you could move from SOAP to Rest as a delivery method, and the JSON returned has less overhead than the XML that Soap uses...which will improve performance a bit more....but, I believe the difference you are reporting is not a web service problem, but an amount of data difference. On Tue, Nov 24, 2015 at 9:28 AM, Terry Bootsma <[email protected]> wrote: > ** > > Environment: > > MidTier Version: 8.1.SP02 Patch 001 201506122355 Hotfix > > Java Version: 1.8.0_40 > > Web Server: Apache Tomcat/7.0.53 > > OS : Red Hat Linux > > I'd be interested in getting feedback from anyone who is utilizing BMC Web > Services and their performance when it comes to larger amounts of data. > > For example... > > I am querying a form that returns ~ 500 incidents. If I query the form > directly via a browser from the ARSystem MidTier, the response time is < 2 > seconds. If I submit the same query via web-services (same underlying > form) , the response ~= 13 seconds. I know that there is overhead > associated with SOAP/XML processing, but if anyone has come across any > tricks/tuning specifically for Web Services, I would be interested in > hearing from you . > > Thank you > > Terry > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
