The OPTMILP Option Tuner
The tuner creates several Output Delivery System (ODS) tables by default unless you specify a value other than 1 for the PRINTLEVEL= option in the PROC OPTMILP statement. The names of these tables are listed in Table 14.7. The TunerInfo and TunerSummary tables contain the tuner’s input summary and results summary, respectively. The TunerResults table contains the option values, geometric mean and summation of the solution times, success rate for the initial option configuration, and a selection of best option configurations and worst option configurations.They are sorted according to the success rate and performance measure specified by the GOAL= option. The Config 0 column contains the solution information of either the initial values that you provided or the solver default values for the options.
The “Performance Information” table is produced by default. It displays information about the execution mode. For single-machine mode, the table displays the number of threads used. For distributed mode, the table displays the grid mode (symmetric or asymmetric), the number of compute nodes, and the number of threads per node.
If you specify the DETAILS option in the PERFORMANCE statement, the procedure also produces a “Timing” table in which the accumulated elapsed times (absolute and relative) for the main tasks of the procedure are displayed.
You can create output data sets from these tables by specifying the ODS OUTPUT statement. For more information about ODS, see SAS Output Delivery System: User's Guide.
Table 14.7: ODS Tables Produced by the OPTMILP Option Tuner
|
ODS Table Name |
Description |
|
PerformanceInfo |
Performance information |
|
Timing |
Timing report |
|
TunerInfo |
Summary of option tuning input |
|
TunerResults |
Option tuning results |
|
TunerSummary |
Summary of option tuning results |
Figure 14.3 shows an example PerformanceInfo table for single-machine mode.
Figure 14.3: Example Tuner Output: PerformanceInfo
| Performance Information | |
|---|---|
| Execution Mode | Single-Machine |
| Number of Threads | 4 |
Figure 14.4 shows an example Timing table.
Figure 14.4: Example Tuner Output: Timing
| Procedure Task Timing | ||
|---|---|---|
| Task | Time (sec.) |
% Time |
| Data Loading | 0.53 | 0.01% |
| Data Transfer | 0.00 | 0.00% |
| Tuner | 0.76 | 0.02% |
| Solver | 4894.80 | 99.95% |
| Idle | 1.40 | 0.03% |
Figure 14.5 shows an example TunerInfo table.
Figure 14.5: Example Tuner Output: TunerInfo
| Tuner Information | |
|---|---|
| Target Solver | MILP |
| Number of Tuning Options | 3 |
| Number of Tuning Instances | 2 |
| Tuning Option Set | USER |
| Performance Goal | GEOMEAN |
| Tuner Time Limit | 1200 |
| Tuner Configurations Limit | 2147483647 |
Figure 14.6 shows an example TunerResults table.
Figure 14.6: Example Tuner Output: TunerResults
| Tuner Results | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Config 0 | Config 1 | Config 2 | Config 3 | Config 4 | Config 5 | Config 6 | Config 7 | Config 8 | Config 9 | Config 10 | |
| cutclique | -1 | -1 | 2 | -1 | -1 | -1 | -1 | 1 | 0 | 2 | -1 |
| cutgomory | -1 | -1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | -1 | 2 |
| heuristics | -1 | 2 | 2 | 2 | 0 | 2 | 3 | 1 | 3 | 3 | 3 |
| Mean of Run Times | 86.11 | 72.77 | 76.72 | 79.96 | 82.16 | 89.96 | 108.19 | 108.79 | 111.71 | 93.49 | 62.7 |
| Sum of Run Times | 176.16 | 147.99 | 156.56 | 162.85 | 179.53 | 183.26 | 236.56 | 224.39 | 240.38 | 195.28 | 125.5 |
| Percentage Successful | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 50 | 0 |
Figure 14.7 shows an example TunerSummary table.
Figure 14.7: Example Tuner Output: TunerSummary
| Tuner Summary | |
|---|---|
| Actual Tuning Time | 1254.35 |
| Initial Run Time (geomean) | 86.11 |
| Initial Run Time (sum) | 176.16 |
| Best Run Time (geomean) | 72.78 |
| Best Run Time (sum) | 147.99 |
| Number of Improved Configurations | 4 |
| Number of Tested Configurations | 24 |