Performance

You can maximize performance in the Graphical Scheduling application by limiting the query size of your schedules and adjusting other settings.

The following suggestions can help maximize performance.

• Break schedules up into smaller queries. Work on smaller data groups within a larger schedule. Only the information that has changed is saved. For example, if you are working on a group of 20 work orders in the middle of a schedule containing 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.
• Set your applet memory higher. Ensure that you have the latest Java™ plug-in, version 1.6.0_14 or above, installed on the computer where Maximo® resides. With the Gantt view of the Graphical Scheduling application open, right-click on the Java icon in the lower-right of your system's taskbar. Select Open Control Panel from the menu. Click the Java tab. In the Java Applet Runtime Settings panel, click the View button. Double-click the Java Runtime Parameters column. Enter a memory setting (for example, 512 mb) using the syntax -Xmx512m then click OK and restart the browser.
• 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 you want to allow Graphical Scheduling to retrieve at a time. Select the Live Refresh action to activate the new setting.
• 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. The user 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 you want to allow Graphical Scheduling to commit while running in real time (the default is 500). Select the Live Refresh action to activate the new setting.