|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  MQWorkflow Performance Optimisation | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | pingwf | 
		  
		    
			  
				 Posted: Thu Jan 30, 2003 10:36 pm    Post subject: MQWorkflow Performance Optimisation | 
				     | 
			   
			 
		   | 
		 
		
		   Novice
 
 Joined: 09 Dec 2002 Posts: 23
  
  | 
		  
		    
			  
				Dear All,
 
I have a MQWorkflow environment here I want to optimise or fine tune it for best performance. MQ Workflow server is running on AIX and Web client set up with 3 dedicated WAS Win2k machine having Workflow client with Q managers. 
 
 
At peak hours total work items goes above 9000 and process instance goes above 8000 and also expected the load on Workflow will increase.
 
 
Currently these are the setup for MQ Workflow Server. 
 
 
-    Execution server settings
 
-       Check interval                         PT5M
 
-       Number of initial server instances     2
 
-       Immediate cleanup                      No
 
-       Navigation transaction threshold       1999999999
 
 
 
-    Cleanup server settings
 
-       Check interval                         PT5M
 
-       Start mode                             Deferred
 
-       Server start time                      Everyday at 00:00
 
-       Server stop time                       06:00
 
-       Cleanup time                           P1W
 
-       Cleanup delay time                     PT1H
 
 
We are performing reorg on FMCDB to optimise the runtime database.
 
 
Following are the action plans i m thinking for performance:
 
1. Start one or two more Execution server Instance.
 
2. Start the cleanup server before the peak hours so it will clean up the FMCDB database.
 
Please let me know what other things need  to be considered for optimisation
 
 
Thanks
 
DKP | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | Ratan | 
		  
		    
			  
				 Posted: Fri Jan 31, 2003 9:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand Master
 
 Joined: 18 Jul 2002 Posts: 1245
  
  | 
		  
		    
			  
				Hi,
 
 
Depending on your harware resources you might want to start more ES. I always start 4 ES. 
 
 
Where does your WF DB2 server reside? I would have a 3-tier setup.
 
 
As you said you had 3 WAS machines and 1 WF machine. I would consider adding a WF machine. 
 
 
If there is any possibilty to decrease the Number of Workitems, It is very helpful.
 
 
-Laze | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | pingwf | 
		  
		    
			  
				 Posted: Sat Feb 01, 2003 6:17 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Novice
 
 Joined: 09 Dec 2002 Posts: 23
  
  | 
		  
		    
			  
				Laze,
 
 
MQ WF server is running on AIX HACMP server so there is enough resource to run 2more ES instances.
 
 
We have 2Tier Setup, DB2 and Workflow both are in AIX server.
 
 
We have 1 to 1 mapping between workitems and WF users . The load on workflow is increasing as bussiness demand is expanding so there is no way to decrease workitems.
 
 
 
Thanks 
 
 
DKP | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | dkrawczynski | 
		  
		    
			  
				 Posted: Tue Feb 04, 2003 9:49 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Apprentice
 
 Joined: 19 Dec 2002 Posts: 26 Location: Dallas, TX 
  | 
		  
		    
			  
				Performance tuning of the MQWF product is a complicated process that should include analysis of how you are using the product.  If you have a multi processor machine running your WF, the bottle neck is usually I/O and not CPU.  Some general performance improvement techniques are:
 
 
1) Increase the number of execution servers.  On multi-processor UNIX systems about 4 is the optimum number, adding more increases performance by only a few percent.  I've tested on a zOS machine and 5 was the optimum number.
 
 
2) Install the MQSeries Queue manager used by the workflow server on a different disk than the DB2 database used by the workflow server.  Separate disks for MQSeries data and logs would be optimum.
 
 
3) Move the high volumne runtime tables spaces(WORKITEM, INSTINDX) to separate disks.
 
 
4) If you are using the audit trail, place it's table space on a different disk as well.
 
 
5) As always, defer clean up until off-peak hours as you already know.  I would run some tests to make sure that the clean up server has an adequate amount of time to run (6 hours may not be enough in some cases.)
 
 
I don't have any experience, but I would speculate the moving to a 3-tier setup would only be beneficial if you did not have additional disks to support suggestions 3 & 4 above and you had a high speed network connection between DB2 and the MQWF server.  Does anyone have experience with performance testing 2-tier vs. 3 tier?
 
 
Here are two support packs that are related to MQWF performance.
 
 
http://www-3.ibm.com/software/ts/mqseries/txppacs/wp01.html
 
http://www-3.ibm.com/software/ts/mqseries/txppacs/wp11.html _________________ Doug Krawczynski
 
IBM Certified Solutions Expert - 
 
MQSeries Workflow | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | 
		    
		   | 
		 
	   
	 | 
   
 
  
	     | 
	 | 
	Page 1 of 1 | 
   
 
 
 
  
  	
	  
		
		  
 
  | 
		  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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |