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).
    Note that some very long lines in this section may be truncated by your web browser !
  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

Namesubmitted/manquinho/routing/normalized-s3-3-3-5pb.opb
MD5SUM1f2ea0bfe66b5e24f2472dc653822ec1
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 34
Optimality of the best value was proved YES
Number of terms in the objective function 240
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 240
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 3
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 240
Number of bits of the biggest sum of numbers8
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.228964
Number of variables240
Total number of constraints646
Number of constraints which are clauses634
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 constraint20

Trace number 9675

Launcher Data

LAUNCH ON wulflinc11 THE 2005-09-23 15:02:23 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8438 boxname=wulflinc11 idbench=234 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  1f2ea0bfe66b5e24f2472dc653822ec1  /oldhome/oroussel/tmp/wulflinc11/normalized-s3-3-3-5pb.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc11/normalized-s3-3-3-5pb.opb
IDLAUNCH: 8438
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.045
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	: 888.83

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.045
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:        919200 kB
Buffers:          8260 kB
Cached:          82112 kB
SwapCached:          0 kB
Active:          55116 kB
Inactive:        44820 kB
HighTotal:      131008 kB
HighFree:        46564 kB
LowTotal:       903652 kB
LowFree:        872636 kB
SwapTotal:     2097136 kB
SwapFree:      2097136 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6976 kB
Slab:             9724 kB
Committed_AS:    63628 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-23 15:02:28 (client local time) WITH STATUS 30 IN 4.80927 SECONDS
stats: 8438 0 4.80927 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 36
c small objective detected
c CONFLICT during preprocess 
c [startup+0.568457 s]  setting bit 7 to 0
c CONFLICT during preprocess 
c [startup+0.5929 s]  setting bit 6 to 0
c [startup+0.651124 s]  setting bit 5 to 0
c [startup+1.26244 s]  setting bit 4 to 0
c [startup+2.52181 s]  setting bit 3 to 0
c [startup+3.5588 s]  setting bit 2 to 0
c [startup+4.57589 s]  setting bit 1 to 0
c got solution with objective value: 34
c [startup+4.8704 s]  setting bit 0 to 1
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 -v25 -v26 -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

Watcher Data

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGTERM then SIGKILL): 921600 Kb
Enforcing VSIZE limit: 994918400 bytes
Current StackSize limit: 67108864 bytes
Raw data (/proc/7864/stat): 7864 (pb2sat) R 7863 7864 4060 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 21113323 1527808 2 4294967295 134512640 135987407 3221224560 3221224560 134512928 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/7864/statm): 373 2 364 364 0 9 0
[pid=7864] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc11/normalized-s3-3-3-5pb.opb
One traced child (pid=7864) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 4.89536
CPU time (s): 4.80927
CPU user time (s): 4.70628
CPU system time (s): 0.102984
CPU usage (%): 98.2413
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	34