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/primes-dimacs-cnf/normalized-jnh210.opb
MD5SUM536a635f83fc17dc00978c285b2ea8e6
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 88
Optimality of the best value was proved YES
Number of terms in the objective function 200
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 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
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 benchmark1.3198
Number of variables200
Total number of constraints900
Number of constraints which are clauses900
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint10

Trace number 9616

Launcher Data

LAUNCH ON wulflinc26 THE 2005-09-23 14:48:09 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=8378 boxname=wulflinc26 idbench=174 idsolver=8 numberseed=0
MD5SUM SOLVER: 
MD5SUM BENCH:  536a635f83fc17dc00978c285b2ea8e6  /oldhome/oroussel/tmp/wulflinc26/normalized-jnh210.opb
REAL COMMAND:  pb2sat /oldhome/oroussel/tmp/wulflinc26/normalized-jnh210.opb
IDLAUNCH: 8378
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.055
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	: 3
cpu MHz		: 451.055
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:        929340 kB
Buffers:         10644 kB
Cached:          77824 kB
SwapCached:          0 kB
Active:          44148 kB
Inactive:        47176 kB
HighTotal:      131008 kB
HighFree:        50232 kB
LowTotal:       903652 kB
LowFree:        879108 kB
SwapTotal:     2097892 kB
SwapFree:      2097892 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           6972 kB
Slab:             8352 kB
Committed_AS:    63620 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-09-23 14:48:24 (client local time) WITH STATUS 30 IN 14.8887 SECONDS
stats: 8378 0 14.8887 30

Solver Data

c This solver internally uses Chaff 2004.11.15 Simplified
c running zchaff...
c got solution with objective value: 100
c small objective detected
c CONFLICT during preprocess 
c [startup+0.809822 s]  setting bit 7 to 0
c [startup+1.24062 s]  setting bit 6 to 0
c [startup+2.0317 s]  setting bit 5 to 0

c Decision: 7115/15361	Time: 2.84457/86400
c [startup+5.45527 s]  setting bit 4 to 0

c got solution with objective value: 91
c [startup+5.87743 s]  setting bit 3 to 1

c [startup+12.6107 s]  setting bit 2 to 0

c got solution with objective value: 89
c [startup+14.3306 s]  setting bit 1 to 1

c got solution with objective value: 88
c [startup+15.0258 s]  setting bit 0 to 1
s OPTIMUM FOUND
v -x1 -x10 -x100 -x101 x102 x103 -x104 x105 -x106 -x107 -x108 x109 -x11 -x110 x111 -x112 x113 -x114 x115 -x116 -x117 x118 -x119 -x12 x120 x121 -x122 -x123 x124 x125 -x126 x127 -x128 -x129 -x13 x130 -x131 -x132 x133 -x134 -x135 x136 -x137 x138 -x139 x14 x140 x141 -x142 x143 -x144 -x145 x146 x147 -x148 x149 x15 -x150 x151 -x152 x153 -x154 -x155 x156 -x157 -x158 x159 -x16 -x160 x161 -x162 -x163 x164 x165 -x166 x167 -x168 -x169 -x17 x170 x171 -x172 -x173 x174 x175 -x176 x177 -x178 -x179 x18 -x180 -x181 -x182 -x183 x184 x185 -x186 -x187 x188 x189 -x19 -x190 x191 -x192 x193 -x194 -x195 x196 x197 -x198 -x199 x2 -x20 -x200 -x21 x22 -x23 -x24 -x25 x26 -x27 -x28 x29 -x3 -x30 -x31 -x32 x33 -x34 x35 -x36 -x37 x38 -x39 x4 x40 -x41 x42 -x43 x44 -x45 x46 x47 -x48 x49 -x5 -x50 x51 -x52 x53 -x54 -x55 -x56 -x57 x58 x59 x6 -x60 -x61 x62 x63 -x64 x65 -x66 -x67 x68 x69 -x7 -x70 x71 -x72 -x73 x74 -x75 x76 x77 -x78 -x79 x8 x80 x81 -x82 x83 -x84 x85 -x86 -x87 x88 x89 x9 -x90 -x91 x92 -x93 x94 x95 -x96 -x97 x98 x99 

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/6763/stat): 6763 (pb2sat) R 6762 6763 4005 0 -1 0 18 0 0 0 0 0 0 0 24 0 1 0 20991891 1527808 2 4294967295 134512640 135987407 3221224576 3221224576 134512928 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/6763/statm): 373 2 364 364 0 9 0
[pid=6763] vsize: 1492
open syscall for file /oldhome/oroussel/tmp/wulflinc26/normalized-jnh210.opb

[startup+10.0017 s]
Raw data (loadavg): 0.79 0.92 0.97 2/55 6763
Raw data (/proc/6763/stat): 6763 (pb2sat) R 6762 6763 4005 0 -1 0 2649 0 0 0 976 12 0 0 25 0 1 0 20991891 9928704 2019 4294967295 134512640 135987407 3221224576 3221223120 134811839 0 0 5 16384 0 0 0 17 0 0 0
Raw data (/proc/6763/statm): 2424 2019 364 364 0 2060 0
[pid=6763] vsize: 9696
Current children cumulated CPU time (s) 9.88
Current children cumulated vsize (Kb) 9696
One traced child (pid=6763) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 15.0611
CPU time (s): 14.8887
CPU user time (s): 14.7238
CPU system time (s): 0.164974
CPU usage (%): 98.8558
Max. virtual memory (cumulated for all children) (Kb): 9696

Verifier Data

Verifier:	OK	88