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 PerformanceInfo table appears under shared or distributed parallel mode. The TunerInfo and TunerSummary tables contain the tuner’s input summary and results summary, respectively. The TunerResults table contains the option values, the geometric mean and summation of the solution times, and the number of failed solution attempts for the initial option configuration, the best option configurations, and the worst option configurations. 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 when the tuner is called with multiple threads.
Figure 14.3: Example Tuner Output: PerformanceInfo
Performance Information | |
---|---|
Execution Mode | On client |
Number of Threads | 4 |
Figure 14.4 shows an example Timing table when the tuner is called with multiple threads.
Figure 14.4: Example Tuner Output: Timing
Procedure Task Timing | ||
---|---|---|
Task | Time (sec.) |
% Time |
Data Loading | 0.23 | 0.06% |
Data Transfer | 0.00 | 0.00% |
Tuner | 0.81 | 0.19% |
Solver | 416.46 | 99.62% |
Idle | 0.55 | 0.13% |
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 | 100 |
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 | 0 | -1 | 0 | 0 | 0 | 1 | -1 | -1 | 1 | 1 |
cutgomory | -1 | 2 | 0 | -1 | 1 | -1 | 1 | 1 | 1 | 1 | 0 |
heuristics | -1 | 0 | 1 | 2 | 0 | 3 | 3 | 0 | 1 | -1 | 1 |
Run Time (Mean) | 5.981747 | 5.701321 | 5.707707 | 5.714656 | 5.714656 | 5.715718 | 6.296905 | 6.31372 | 6.314053 | 6.401778 | 6.653233 |
Run Time (Sum) | 11.964 | 11.418 | 11.435 | 11.45 | 11.45 | 11.452 | 12.605 | 12.635 | 12.638 | 12.807 | 13.308 |
Num of Failed | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Figure 14.7 shows an example TunerSummary table.
Figure 14.7: Example Tuner Output: TunerSummary
Tuner Summary | |
---|---|
Actual Tuning Time | 107.67 |
Initial Run Time (geomean) | 5.98 |
Initial Run Time (sum) | 11.96 |
Best Run Time (geomean) | 5.70 |
Best Run Time (sum) | 11.42 |
Number of Improved Configurations | 24 |
Number of Tested Configurations | 40 |