UWL/Workflow Performance Recommendations?

[Mike Pokraka]

Hi Jocelyn, 

 

The one I see most is workflows not completing - i.e. the design doesn't
ensure it finishes, users generate lots of workflows that are abandoned in
an 'in processing' state; or it's set up to send IDOC-tasks to WF-BATCH to
sweep them under the carpet (surprisingly common).

 

Not sure about UWL impact, but it definitely slows down SBWP and many of the
WF admin transactions (SWI2_*),  because the WI status is indexed and many
of the SELECT's only look at items that are in READY or STARTED. So even if
your user only has 100 items in the SBWP it will still be slow due to the
extra time taken to ignore several million useless items that are still
considered 'active'. 

 

My usual suggestion: If you're not 100% sure a process is going to finish,
put a long deadline on it after which it's definitely obsolete and cancel
the WF. 

 

Cheers, 

Mike

 

 

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dart, Jocelyn
Sent: 07 November 2008 06:08
To: SAP Workflow Users' Group; SAP Workflow Users' Group
Subject: UWL/Workflow Performance Recommendations?

 

Hi Folks, 

 

Ok I know of some performance issues to watch out for but to be thorough I'd
really appreciate it if the WUG-gers would please share any specific UWL or
Workflow performance recommendations you have come across. 

 

I'm talking about recommendations for relatively recent systems here - EP
7.0 portal against ECC 5.0 or higher, or other NW7.0 systems. 

 

If you would be kind enough to send them through I'm happy to collate them
together for the group, and also share them with Ginger Gatling re future
plans for UWL/workflow development.

 

Really appreciate your assistance with this. 

 

Kind regards,

Jocelyn 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090206/3a977578/attachment.htm