View Single Post
  #5 (permalink)  
Old April 23rd, 2008, 13:15
cspadola cspadola is offline
Member
 
Join Date: Feb 2008
Posts: 31
Thanks: 8
Thanked 0 Times in 0 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 0
cspadola is on a distinguished road
Re: Planning parameters and properties in v5.5 to improve Bulk Planning

Can someone tell me if there is a disadvantage to increasing the number of threads that the batch event uses in the Event Diagnosis? We have a scenario where most of our bulk planning (90% or so) all occurs at the same time each day (starting at 16:00). Currently, the number of threads is set to the default of 2. When a user runs a bulk plan earlier in the day - even with just 30 orders - it takes 1-2 mins to complete. This has become the accepted performance based on our itineraries and characteristics of our orders.

However, when 16:00 rolls around each day and almost all the users run their respective bulk plans simultaneously, there is a queue built up. Bulk planning for each user increases to 10-13 mins each.

Can we safely increase this thread to 4 or even more? Are there any planning parameters I can look at to make this perform better?

We are running OTMv55-CU03 on Linux servers.
Reply With Quote