We found in our project that the shift from User Tool (thick client) to the Mid-Tier as the primary interface is very hard for users to digest, and we see approx. 4 - 5 second render times for screens, it's not that this is 'slow' it's just that the switch from UT to MT is something users have to get used to.
On Sun, Jun 19, 2011 at 10:59, patchsk <[email protected]> wrote: > Thanks, did your users also complained 4 sec as very slow, or it is > just our users not yet able to digest the shift from a thick client > based remedy to browser based. > We are using best practice view, to me it should be a lot faster than > classic view because it has lot less fields on the view compared to a > classic view, so the rendering time should be much more less after an > initial caching. > > On Jun 19, 6:52 am, "Chowdhury, Tauf" <[email protected]> wrote: > > We're on 7.6.04 and seeing similar times but we are on Classic View so it > you can add a second for the redirect. The consoles really depend on how > many requests are in the queue upon loading and what the default filter > settings are. Ours are set to not show closed requests and then it's really > up to the user. > > > > > > > > > > > > > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) on behalf of patchsk > > Sent: Sat 6/18/2011 7:53 PM > > To: [email protected] > > Subject: midtier itsm screen load times average time > > > > We are on ITSM 7.6.03. > > We are seeing on the web New Incident, Search Incident, New Change, > > Search Change screens on average are taking 4 sec, this is after a > > complete midtier caching and user browser caching ( user already > > opened the screens few times before we take the time measurement). > > Incident Console, Change Consoles are taking 8 sec to load. > > Can others using ITSM 7/7.6.03/7.6.04 provide average times that they > > are seeing in their system. > > So that I can see if our performance is too slow or this is what > > others also seeing. > > I went through the BMC benchmark manual, but I am more interested to > > here from real users. > > > > > ___________________________________________________________________________ > ____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" > > > > ********************************************************************** > > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging to Forest Laboratories, Inc. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If > you are not the intended recipient of this e-mail, or the employee or agent > responsible for delivering this e-mail to the intended recipient, you are > hereby notified that any dissemination, distribution, copying or action > taken in relation to the contents of and attachments to this e-mail is > strictly prohibited and may be unlawful. If you have received this e-mail in > error, please notify the sender immediately and permanently delete the > original and any copy of this e-mail and any printout. > > > > > ___________________________________________________________________________ > ____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > 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"
