Your experience with performance

[Jensen, Ralph]

Dale,
 
Regarding your comment on, "an archiving/reorganization strategy.  Depending
on what processes you are running with workflow, the work item retention
requirements could be quite varied by process area."
 
What are some of the considerations in specific?  What should we look for
with regards to processes within workflow and work item retention
requirements?  Can you share with us on what are some of those requirements?
An example of some questions we should be asking our customers.
 
Are you aware of a documented archiving/reorg strategy that SAP recommends
to their customers?
 
Thank you for your contributions to the group.
 
Regards,
RJ
 
-----Original Message-----
From: Dale Davis [mailto:dkdavis at us.ibm.com]
Sent: Tuesday, February 26, 2002 9:45 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Your experience with performance
 
 
Karsten:
 
 I have worked with several implementations where the daily workitem
volumes compare to yours. Not sure what release you are on, but based on my
experience, with 4.5B, you can sustain for 12 to 18 months without
noticeable performance degradation. That of course depends on the capacity
of the system your are running on, the % usage during peak times and the
other processes running.  Also limit the number of general tasks you have
in your system. That costs quite a bit of performance . Replace the general
classification where possible with agent assignments to jobs,orgs ,
positions  or workcenters. To avoid performance problems down the road,  I
recommend you start workfing on an archiving/reorganization strategy soon.
Depending on what processes you are running with workflow, the workitem
retention requirements could be  quite varied by process area. However once
you gather that info, the rest is straightforward and you can schedule your
archive jobs to run periodically. If your analysis shows that workflow is
the best solution for your business problems, then you should use workflow.
There is no reason not to.
 
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow & PP Consultant - SAP Practice
 
IBM Global Services
Phone: 919-543-7678
               T/L 8-441-7678
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to
lose sight of the shore..........
 
 
Karsten Ernst <ernst-consulting at gmx.net>@MITVMA.MIT.EDU> on 02/26/2002
10:05:03 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Your experience with performance
 
 
 
Hi all !
 
Has anyone of you made any experience with performance concerning workflow?
 
We are talking about 10,000 to 50,000 (ten to fifty thousand!) workflows,
and the same number of workitems sure, which will be started one day. These
workitems will then be worked with in 2 or 3 days and then there will be
once more 20,000 workitems started and wait for the users in the inbox.
 
The most critical problem I see are the role resolution to get the user or
organizational unit to execute a workitem. But if we leave this out of
sight, is it a problem for the system to handle the above mentioned number
of workitems?
 
Will there be a slow down of the system if there are 20,000 to 50,000
workitems waiting? Is the workflow engine running all the time or is it
only
acitivated if a workitem is executed?
 
I hope to hear from you soon, as we have to decide to use workflow for this
amount of activities or any other technical solution.
 
Best regards,
 
Karsten