Performance considerations for scheduling work
You can improve performance when scheduling work by limiting the query size of your schedules and adjusting other settings.
The following suggestions can improve performance:
- Break schedules up into smaller queries. Work on smaller data groups within a larger schedule. Only the information that changed is saved. For example, assume that you are working on a group of 20 work orders in the middle of a schedule that contains 300 work orders. Click Perform Critical Path Method on Selected Rows instead of Perform Critical Path Method on All Rows when adjusting the dates and links for the work. There are fewer changes to save and commit.
- Create the schedule at a work order level if the tasks are descriptive in nature and do not affect schedule scope. Clear the Include Tasks in Schedule check box in the Work Order Tracking application to bring only the work order into the schedule. If you want to see resources used by that work order, plan them at the work order level rather than at the task level.
- Limit the number of records that can be retrieved by a saved query at a time. Limiting the number of records can prevent users from inadvertently creating queries that retrieve too many records into the Gantt view (the default is 1000). To limit the record count, in the System Properties application, open the mxe.skd.populatecount record. In the Global Value field, enter the number of records that you want to allow Scheduler to retrieve at a time. From the Select Action menu, choose Live Refresh to activate the new setting.
- When modifying multiple work records at the same time in the graphical view (by using right-click options), limit the number of records you select at one time. Changes to large groups of work records affect performance.
- Specify when the commit operation is run in the background by configuring asynchronous processing. You can limit the number of records that can be committed at a time before the commit transaction is sent to a background, or asynchronous, process. You can then continue to work on other schedules. The schedule that is being committed remains in a read-only state until the commit is complete. To limit the record count, in the System Properties application, open the mxe.skd.changecount record. In the Global Value field, enter the number of records that you want to allow Scheduler to commit while running in real time (the default is 500). From the Actions menu, choose Live Refresh to activate the new setting.
- In Graphical Scheduling projects, clearing the Enable Related Attributes? check box can significantly reduce time when rendering the graphical view. Including attributes from related tables affects performance.