ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Workflow performance

Post new topic  Reply to topic
 Workflow performance « View previous topic :: View next topic » 
Author Message
Liquid
PostPosted: Fri Jun 01, 2007 5:05 am    Post subject: Workflow performance Reply with quote

Acolyte

Joined: 08 Sep 2004
Posts: 52
Location: Hungary, Europe

Hello!

We'we a workflow user interface which collects workitems based on process instance global container values.
So, the WF API query collects all the workitems' which process inscance has the same global container member value.

In the production system it could take for 20-30 seconds to give back the query result.
BUT if we run the query (within some seconds) again, the same wf API call returns in 1-2 seconds. It seems that somewhere in the workflow layers (execution service or DB2...) there are some kind of cache(es).



Has anybody have any explanations why workflow behaves like this?

And which is more important, is there any suggestions or guide to speed up the first query?? (like indexing the GCON... tables, or rebuild other workflow db table indexes, or start more execution services etc)

Is there any MQ WF performance guide like a redbook or similar??


I can explain the whole wf architecture in more details too.
Thanks in advance,
Liquid
Back to top
View user's profile Send private message
jmac
PostPosted: Fri Jun 01, 2007 5:32 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

I don't know if these cover your specific issue, but there are generally three resources I look to for performance type information
    WA0B WebSphere MQ Workflow - Best Practices Guide
    WP01 MQSeries Workflow - Performance estimates for solution and capacity assessments
    WD02 WebSphere MQ Workflow - Considerations for production roll out


These may be found at:
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27007197#6
I do not recall any mention of GDC queries in these, but I am not certain.

Since an index can be defined through the BuildTime interface, I am CERTAIN that it will help.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
hos
PostPosted: Sun Jun 03, 2007 10:40 pm    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,

are you saying that you call the same API against the same DB twice and that it returns the same result but within completely different resonse times? And always the first call needs 20 - 30 seconds?

If this is the case, I agree that there is some result caching that seems to take effect. DB2 has features to keep the result in memory in order to re-use it. MQWF hasn't.

In order to improve the response time of your first run, I suggest traditional DB maintenance and performance tuning. The MQWF Installation Guide contains an appendix how to optimize the runtime DB. Further tools and guidance can be found in the DB2 documentation. Introducing an index can certainly help, but must be handeled with care because it can spoil the performance as well.
Back to top
View user's profile Send private message
tsrisudh
PostPosted: Mon Jun 04, 2007 2:57 am    Post subject: Reply with quote

Centurion

Joined: 11 Aug 2005
Posts: 113

We too had performance problem with query items returning slow, we were using one particular field in the GC to retrieve the process instances, when we created an Index (In the Workbech itself) and redeployed the FDL, the performance improved significantly, also the CPU utilization also improved.

One more change which we did was to increase the bufferpool in the WF DB2, this too helped in the performance.
_________________
Srisudhir Tadepalli
Back to top
View user's profile Send private message Yahoo Messenger
Liquid
PostPosted: Thu Jun 07, 2007 2:14 am    Post subject: Reply with quote

Acolyte

Joined: 08 Sep 2004
Posts: 52
Location: Hungary, Europe

Hello Guys!

Thanks for the replys for all of you.
I downloaded the guides and starts to play around the DB. It was quite certain that we've to tune the DB but now you made it obviously.
I'll let you know the results.

Sorry for the slow answer, I had a flu or something.
Regards,
Liquid
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Workflow performance
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.