Thanks Robert for this follow-up.

As you and I talked offline, web-service is only the interface that the client 
uses here, so the back-end computing seems to be the bottleneck in your Env.

Perf Tuning WP (on Support) might help out for the database or AR Server tuning.

Note: in case Remedy User was quick, but browser and web-services were slow, 
this doc could also could have been used to improve mid-tier Perf (since 
web-services are exposed through the mid-tier).

Take care,

~ Matt Laurenceau
Senior Community Ambassador, BMC Communities
[email protected]
Follow me @Matt_L
Skype: matt.laurenceau 


On 21 sept. 2011, at 17:57, Robert Molenda <[email protected]> wrote:

> ** Thanks Matt - I had that brain cramp after sending the message yesterday...
> 
> The Web-Service timings actually are within the same timeframes as 
> utilization of the Native Client or Web-Client to perform the same types of 
> operations... the differences were negligible as in sub-second differences..
> 
> Thanks again
> Robert 
> 
> On Wed, Sep 21, 2011 at 2:58 AM, Matt Laurenceau <[email protected]> 
> wrote:
> ** Hi Robert.
> 
> Do these figures match with the time it takes to search/create/update 
> incidents using Remedy User Windows client or browser through mid-tier ?
> Just to set expectations, what version of AR / mid-tier is it ?
> 
> I'll get feedback from BMC Engineering.
> 
> How did you "ask BMC" for these resources ? Who did you ping ?
> 
> Regards,
> 
> ~ Matt Laurenceau, BMC Software
> Senior Community Ambassador, BMC Communities
> [email protected]
> Follow me at @Matt_L
> Skype: matt.laurenceau 
> 
> 
> On Tue, Sep 20, 2011 at 7: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"_
> 
> 
> 
> -- 
> 
> ~ Matt Laurenceau, BMC Software
> Senior Community Ambassador, BMC Communities
> [email protected]
> Follow me at @Matt_L
> Skype: matt.laurenceau 
> 
> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
> 
> 
> _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"

Reply via email to