Performance issue deadline monitoring

[Van der Burg, Jeroen JA SITI-ITPSEE]

Hi Koenraad, can you give a bit more info?
 
If you problem is the load of waiting workitems being started at the =
same time you could consider some crude mechanism, eg only restart the =
workitems which are non-urgent after office hours (if you do not have a =
24 hour system).=20
 
If the problem is a limited number of dialogue processes due to an =
increase of your system load, well, you need more memory and more =
dialogue processes defined. That should be pretty straightforward to =
achieve for your basis support people.=20
 
Or is the issue that, after a deadline workitem was started, a lot of =
validation or processing takes place (in a loop or something till the =
next deadline)? In that case consider reducing the frequency of your =
validations (is once a day sufficient and not every hour?) and simplify =
your validation code if possible.
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: Koenraad Janssens [mailto:koenraad.janssens at sidmar.arcelor.com]
Sent: 19 January 2004 08:41
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Performance issue deadline monitoring
 
 
The problem still isn't solved.  We had the idea that the swwdhex job =
was
the problem but we where cleary mistaken..
Any other suggestions?
 
Kind regards
 
Koenraad Janssens
Sidmar N.V.- ISM
Leverage Team - Programmer
Tel: +32 9 347 35 76
E-mail: koenraad.janssens at sidmar.arcelor.com
 
 
 
 
David.Trant at andrew.com
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
16/01/2004 18:11
Please respond to SAP-WUG
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Performance issue deadline monitoring
 
 
I thought I'd share a lesson learned that is similar to this issue.  We
had a poorly designed workflow that ended up spawning hundreds of
background tasks to check a condition using the parallel processing
feature.  SAP very clearly states that the table used for such parallel
processing should not exceed 100 entries, but we had cases where the =
table
had nearly 1000 entries.  The end result was that the workflow, as in
Koenraad's example, took over all available work processes.  To make
matters worse, as errors occurred, the error handling job RSWWERRE got
bogged down as well.  This wasn't exactly an answer to this question, =
but
hopefully it will help keep someone from making a similar mistake, or
recognize the symptoms if they occur sometime.
 
Enjoy,
David
 
 -----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]  On Behalf Of
Koenraad Janssens
Sent:   Friday, January 16, 2004 7:19 AM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Performance issue deadline monitoring
 
Hello All
 
We have an urgent performance issue.  We use deadline monitoring with
SWWDHEX.  The problem is that the order registrations have increased
enormously the last months.  (that's what you get after a merger)  As a
result also our active workflows have increased.  We use deadline
monitoring for various steps in these workflows.  Our problem now is =
that
everytime SWWDHEX runs a lot off tasks start running at the same time =
and
take over all available dialog steps on the server with a dramatical
result on performance.
 
The question is if there is any way in limiting the amount of dialog =
steps
this event can take in simultaneously.  Any other ideas to tackle this
problem are offcourse more then welcome!
 
Kind regards
 
Koenraad Janssens
Sidmar N.V.- ISM
Leverage Team - Programmer
Tel: +32 9 347 35 76
E-mail: koenraad.janssens at sidmar.arcelor.com
-------------------------------------------------------------------------=
---------------------------------------------------------
There are 10 kinds of people in the world - those who know binary and
those who don't
-------------------------------------------------------------------------=
---------------------------------------------------------
 
 
*************************************************************************=
**********
This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
*************************************************************************=
**********
 
-------------------------------------------------------------------------=
-----------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
-------------------------------------------------------------------------=
-----------------------
[mf2]