Trace number 34294

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 into four (or five) parts:
  1. 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 ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. 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.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. 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 X seconds (see the parameters in the trace). 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 X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    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.
  5. 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 provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerObjective functionCPU timeWall clock time
PB-smodels 1.28OPT200 0.206968 0.168557

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-200-6_0-yes1-3.opb
MD5SUMe81d959a9d7a634134c260bbfba059b7
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark200
Best CPU time to get the best result obtained on this benchmark0.029994
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 200
Optimality of the best value was proved YES
Number of variables400
Total number of constraints1400
Number of constraints which are clauses1395
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints5
Minimum length of a constraint2
Maximum length of a constraint3
Number of terms in the objective function 400
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 400
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 2
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 400
Number of bits of the biggest sum of numbers9
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c Running pbsmodels-v1.28
0.13	o 200
0.16	s OPTIMUM FOUND
0.16	v x2 x3 x6 x7 x10 x11 x14 x16 x18 x19 x21 x24 x26 x28 x29 x32 x34 x35 x37 x39 x41 x43 x46 x47 x49 x52 x54 x55 x58 x59 x62 x63 x66 x68 x70
0.16	v x71 x74 x75 x78 x80 x82 x84 x85 x88 x90 x92 x94 x96 x98 x99 x101 x104 x106 x107 x109 x111 x114 x115 x118 x119 x122 x123 x126 x128
0.16	v x129 x131 x134 x136 x138 x140 x141 x143 x146 x147 x150 x151 x153 x155 x158 x160 x161 x164 x165 x167 x169 x171 x174 x176 x178 x180
0.16	v x181 x184 x186 x187 x190 x192 x193 x195 x197 x200 x202 x204 x206 x208 x210 x211 x213 x216 x217 x219 x222 x224 x225 x228 x230 x231
0.16	v x234 x235 x238 x239 x241 x243 x246 x247 x249 x252 x253 x255 x258 x260 x262 x264 x266 x268 x269 x271 x273 x275 x277 x280 x282 x284
0.16	v x286 x287 x289 x291 x294 x295 x298 x300 x302 x304 x305 x308 x310 x311 x313 x315 x317 x319 x321 x323 x326 x327 x330 x332 x333 x336
0.16	v x338 x340 x341 x343 x346 x348 x350 x352 x353 x356 x357 x359 x362 x363 x366 x368 x369 x371 x373 x376 x377 x380 x382 x383 x385 x388
0.16	v x389 x391 x393 x395 x398 x400 -x1 -x4 -x5 -x8 -x9 -x12 -x13 -x15 -x17 -x20 -x22 -x23 -x25 -x27 -x30 -x31 -x33 -x36 -x38 -x40 -x42
0.16	v -x44 -x45 -x48 -x50 -x51 -x53 -x56 -x57 -x60 -x61 -x64 -x65 -x67 -x69 -x72 -x73 -x76 -x77 -x79 -x81 -x83 -x86 -x87 -x89 -x91 -x93
0.16	v -x95 -x97 -x100 -x102 -x103 -x105 -x108 -x110 -x112 -x113 -x116 -x117 -x120 -x121 -x124 -x125 -x127 -x130 -x132 -x133 -x135
0.16	v -x137 -x139 -x142 -x144 -x145 -x148 -x149 -x152 -x154 -x156 -x157 -x159 -x162 -x163 -x166 -x168 -x170 -x172 -x173 -x175 -x177
0.16	v -x179 -x182 -x183 -x185 -x188 -x189 -x191 -x194 -x196 -x198 -x199 -x201 -x203 -x205 -x207 -x209 -x212 -x214 -x215 -x218 -x220
0.16	v -x221 -x223 -x226 -x227 -x229 -x232 -x233 -x236 -x237 -x240 -x242 -x244 -x245 -x248 -x250 -x251 -x254 -x256 -x257 -x259 -x261
0.16	v -x263 -x265 -x267 -x270 -x272 -x274 -x276 -x278 -x279 -x281 -x283 -x285 -x288 -x290 -x292 -x293 -x296 -x297 -x299 -x301 -x303
0.16	v -x306 -x307 -x309 -x312 -x314 -x316 -x318 -x320 -x322 -x324 -x325 -x328 -x329 -x331 -x334 -x335 -x337 -x339 -x342 -x344 -x345
0.16	v -x347 -x349 -x351 -x354 -x355 -x358 -x360 -x361 -x364 -x365 -x367 -x370 -x372 -x374 -x375 -x378 -x379 -x381 -x384 -x386 -x387
0.16	v -x390 -x392 -x394 -x396 -x397 -x399

Verifier Data (download as text)

OK	200

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

runsolver version 3.0.1 (c) roussel@cril.univ-artois.fr

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node73/watcher-34294-1149638173 -o ROOT/results/node73/solver-34294-1149638173 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node73/34294-1149638173/instance-34294-1149638173.opb 581018965 ROOT/tmp/node73/34294-1149638173 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.95 0.94 3/64 18588
/proc/meminfo: memFree=1495896/2055920 swapFree=4182184/4192956
[pid=18588] ppid=18586 vsize=5360 CPUtime=0
/proc/18588/stat : 18588 (runpbsmodels) S 18586 18588 18542 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 229482045 5488640 234 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 210723464004 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18588/statm: 1340 234 195 169 0 51 0
[pid=18589] ppid=18588 vsize=2504 CPUtime=0
/proc/18589/stat : 18589 (pbsmodels-v1.28) R 18588 18588 18542 0 -1 4194304 43 0 0 0 0 0 0 0 20 0 1 0 229482046 2564096 26 18446744073709551615 4194304 4206940 548682069008 18446744073709551615 210720815453 0 0 4096 0 0 0 0 17 1 0 0
/proc/18589/statm: 626 26 19 3 0 5 0

Child status: 0
Real time (s): 0.168557
CPU time (s): 0.206968
CPU user time (s): 0.183972
CPU system time (s): 0.022996
CPU usage (%): 122.788
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node73 on Tue Jun  6 23:56:13 UTC 2006


FILE ID= 34294-1149638173

PBS_JOBID= 323113

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-200-6_0-yes1-3.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node73/34294-1149638173/instance-34294-1149638173.opb 581018965  ROOT/tmp/node73/34294-1149638173
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node73/watcher-34294-1149638173 -o ROOT/results/node73/solver-34294-1149638173 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node73/34294-1149638173/instance-34294-1149638173.opb 581018965  ROOT/tmp/node73/34294-1149638173

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  e81d959a9d7a634134c260bbfba059b7

RANDOM SEED= 581018965


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.261
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.261
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1496104 kB
Buffers:         32028 kB
Cached:         457900 kB
SwapCached:       2596 kB
Active:          33480 kB
Inactive:       465260 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1496104 kB
SwapTotal:     4192956 kB
SwapFree:      4182184 kB
Dirty:             284 kB
Writeback:           0 kB
Mapped:          15136 kB
Slab:            47120 kB
Committed_AS:   453048 kB
PageTables:       1416 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node73 on Tue Jun  6 23:56:13 UTC 2006