Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided in four parts:
  1. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provide some useful information on the computer.
  2. SOLVER DATA
    This is the output of the solver (stdout and stderr).
  3. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to 1200 seconds. After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to 1230 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (900Mb).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  4. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.

General information on the benchmark

Namenormalized-opb/submitted/manquinho/routing/normalized-s3-3-3-2pb.opb
MD5SUM403e00059390cf58db4a40d0c72aa686
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 36
Optimality of the best value was proved NO
Number of terms in the objective function 264
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 264
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 3
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 264
Number of bits of the biggest sum of numbers9
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.076987
Number of variables264
Total number of constraints712
Number of constraints which are clauses700
Number of constraints which are cardinality constraints (but not clauses)12
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint22

Trace number 7772 

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc3 THE 2005-04-17 16:31:45 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=2085 boxname=wulflinc3 idbench=232 idsolver=6 numberseed=0
MD5SUM SOLVER: 2225cba0d9b2c30e235f6cafc823d7ac  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  403e00059390cf58db4a40d0c72aa686  /oldhome/oroussel/tmp/wulflinc3/normalized-s3-3-3-2pb.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc3/normalized-s3-3-3-2pb.opb
IDLAUNCH: 2085
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.190
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 890.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.190
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        795428 kB
Buffers:         37352 kB
Cached:         177448 kB
SwapCached:       3276 kB
Active:          91232 kB
Inactive:       129704 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        795176 kB
SwapTotal:     2097136 kB
SwapFree:      2093860 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6924 kB
Slab:            12648 kB
Committed_AS:    71676 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1388 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-04-17 16:31:46 (client local time) WITH STATUS 30 IN 0.209967 SECONDS
stats: 2085 0 0.209967 30
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc3/normalized-s3-3-3-2pb.opb ......
c The optimum solution is:36
s OPTIMUM FOUND
v -v1 -v10 -v100 v101 -v102 -v103 v104 -v105 -v106 v107 -v108 -v109 -v11 -v110 -v111 -v112 -v113 -v114 -v115 v116 -v117 -v118 -v119 v12 -v120 -v121 -v122 v123 v124 -v125 -v126 -v127 -v128 v129 v13 -v130 -v131 -v132 v133 -v134 -v135 -v136 -v137 v138 -v139 -v14 v140 -v141 -v142 v143 -v144 -v145 -v146 -v147 -v148 -v149 -v15 -v150 v151 -v152 -v153 v154 -v155 -v156 -v157 -v158 -v159 -v16 -v160 -v161 -v162 -v163 -v164 -v165 -v166 v167 -v168 -v169 -v17 -v170 -v171 -v172 v173 v174 -v175 -v176 -v177 v178 -v179 -v18 -v180 -v181 -v182 -v183 -v184 -v185 -v186 -v187 -v188 -v189 -v19 v190 -v191 -v192 -v193 v194 -v195 -v196 -v197 -v198 -v199 -v2 -v20 -v200 -v201 -v202 -v203 -v204 -v205 v206 -v207 -v208 -v209 -v21 -v210 -v211 -v212 -v213 -v214 -v215 -v216 -v217 -v218 -v219 -v22 -v220 -v221 -v222 -v223 -v224 -v225 -v226 -v227 v228 -v229 -v23 -v230 -v231 -v232 -v233 -v234 v235 -v236 -v237 -v238 -v239 -v24 -v240 -v241 -v242 -v243 -v244 -v245 v246 -v247 -v248 -v249 -v25 -v250 -v251 -v252 -v253 -v254 -v255 -v256 -v257 -v258 -v259 -v26 -v260 -v261 -v262 -v263 v264 v27 v28 -v29 -v3 -v30 -v31 -v32 v33 -v34 -v35 -v36 -v37 -v38 v39 -v4 -v40 -v41 -v42 v43 -v44 -v45 -v46 -v47 -v48 -v49 -v5 -v50 -v51 v52 -v53 -v54 -v55 -v56 -v57 -v58 -v59 -v6 -v60 -v61 v62 -v63 -v64 -v65 -v66 -v67 -v68 -v69 -v7 -v70 -v71 -v72 v73 -v74 -v75 -v76 -v77 -v78 -v79 -v8 -v80 -v81 -v82 -v83 -v84 -v85 -v86 -v87 -v88 v89 v9 -v90 -v91 -v92 -v93 -v94 -v95 -v96 -v97 -v98 -v99 
c Done, CPU Time=0.176973
#### END SOLVER DATA ####
#### BEGIN WATCHER DATA ####
Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing VSIZE limit: 943718400 bytes
Raw data (loadavg): 0.91 0.95 0.90 2/54 4150
Raw data (stat): 4150 (runsolver) R 4149 10720 10719 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 453750989 1052672 99 4294967295 134512640 135381576 3221224528 3221219776 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 1028
[startup+0.213632 s]
Raw data (loadavg): 0.91 0.95 0.90 1/53 4150
Raw data (stat): 4150 (runsolver) R 4149 10720 10719 0 -1 64 4 0 0 0 0 0 0 0 19 0 1 0 453750989 1052672 99 4294967295 134512640 135381576 3221224528 3221219776 135158418 0 2147483391 7 90112 0 0 0 17 0 0 0
Raw data (statm): 257 99 215 215 0 42 0
vsize: 0

Child status: 30
Real time (s): 0.213361
CPU time (s): 0.209967
CPU user time (s): 0.200969
CPU system time (s): 0.008998
CPU usage (%): 98.4093
Max. virtual memory (Kb): 1028
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
Verifier:	OK	36
#### END VERIFIER DATA ####