This is definitely something in how the mid-tier handles web services against the join form. I was hoping that I couldn't be the only one that has experienced this and was hoping someone might chime in with a golden egg. ;-)
Terry On 2015-01-06 12:17, laurent matheo wrote: > ** Hi :) > > I guess you could log and compare and check where the time is consumed when > using the WS. > If API + SQL calls are the same, then it's « elsewhere ». > > Le 6 janv. 2015 à 18:15, Terry Bootsma <[email protected]> a écrit : > > ** > > For further information: > > Remedy User Tool against the join form: < 1 second > > MidTier direct access against the join form: < 5 seconds > > So, it is not a join-form or indexing issue. > > Terry > > On 2015-01-06 12:12, [email protected] wrote: > > Hello everyone: > > I was wondering if anyone else has experienced this. > > Environment: > > Red Hat Linux 6.4 > Mid Tier 8.1.01 SP1 20140514135 Hotfix > Apache Tomcat 6.0 > Remedy Server 8.1.01 201401281910 > Oracle Database > > When consuming web services that are based on "join" forms in Remedy, we have > experienced a significant performance degradation in response time. For > example, to query 2000 rows in the base form with a web service against the > base form, < 3 seconds. If we create a self-join and do the same web service > .. approx 17 seconds. > > Has anyone else seen this? > > Thanks. > > Terry > _ARSlist: "Where the Answers Are" and have been for 20 years_ _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"
