William,

I have seen the same performance issue when an incident is added to an SLM.
COuld you share your environment details and what you have known so far?

Regards,
Emad


On 10/30/07, Howard Richter <[EMAIL PROTECTED]> wrote:
>
> **
>
> William,
>
>
>
> I have seen on our system were you would create the incident, which
> creates the service request and then does the auto assign, in less then 15
> seconds. However the assignment notification could take up to 15 minutes to
> hit the email messages form (and then go out using the engine).
>
>
>
> I have been trying to find a reason for this for months, and I was just
> curious if you were seeing this with the slow incident submit.
>
>
>
> Howard
>
>
>
> On 10/30/07, Robert Halstead <[EMAIL PROTECTED] > wrote:
> >
> > William,
> >
> > We also get a lagged response from Remedy when a ticket is saved.  We
> > haven't been able to track it down to a cause but have been blaming it
> > on the network.  Essentially, the user client shows the ticket number
> > created in the status bar right after the save button is clicked,
> > however, upon save we have it re-open the saved ticket and seems to
> > hang anywhere from 5-15 seconds before it the user tool goes through
> > its stuff to open a new window (UI changes and so forth).
> >
> > I'm not sure if it's the user tool, the remedy server, or the network.
> > Our situation is that the server is barely doing anything so it's
> > hard to trace the problem.
> >
> > BTW, didn't mean to hijack your thread, sorry.
> >
> > Server: Remedy 6.3 patch 21 on Solaris 5.9
> > Database: Oracle
> >
> >
> > On 10/30/07, Howard Richter < [EMAIL PROTECTED]> wrote:
> > > **
> > >
> > > William,
> > >
> > >
> > >
> > > Are you also seeing a delay on the notification
> > >
> > >
> > >
> > > Howard
> > >
> > >
> > >
> > > On 10/30/07, William Rentfrow < [EMAIL PROTECTED]> wrote:
> > > > **
> > > >
> > > > I'm testing some stuff and I'm experiencing very slow Incident
> > submit
> > > times right now.
> > > >
> > > > I'm using SLM 7.03 and Incident 7.02.  I have two service targets
> > defined
> > > for a particular Incident - and submit time has now gone to about 30
> > seconds
> > > for a single Incident.
> > > >
> > > > I'm working through the logs, etc - but is anyone else using SLM
> > with IM?
> > > If so, what sort of "save" times are you getting when you create a new
> > > Incident that has Service Targets that attach?
> > > >
> > > > William Rentfrow, Principal Consultant
> > > > [EMAIL PROTECTED]
> > > > C 701-306-6157
> > > > O 952-432-0227
> > > >  __20060125_______________________This posting was
> > > submitted with HTML in it___
> > >
> > >
> > >
> > > --
> > > Howard Richter
> > >
> > > Remedy ServiceDesk Manager
> > > CedarCrestone Managed Services Center
> > >
> > > [EMAIL PROTECTED]
> > > __20060125_______________________This posting was submitted
> > > with HTML in it___
> >
> >
> > --
> > "A fool acts, regardless; knowing well that he is wrong. The ignoramus
> > acts on only what he knows, but all that he knows.
> > The ignoramus may be saved, but the fool knows that he is doomed."
> >
> > Robert Halstead
> >
> > _______________________________________________________________________________
> >
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> > the Answers Are"
> >
>
>
>
> --
> Howard Richter
>
> Remedy ServiceDesk Manager
> CedarCrestone Managed Services Center
>
> [EMAIL PROTECTED] __20060125_______________________This
> posting was submitted with HTML in it___
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to