Trace number 45725

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.31OPT200 0.196969 0.180062

General information on the benchmark

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

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/node46/watcher-45725-1149652818 -o ROOT/results/node46/solver-45725-1149652818 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node46/45725-1149652818/instance-45725-1149652818.opb 454194854 ROOT/tmp/node46/45725-1149652818 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.95 0.93 2/64 13234
/proc/meminfo: memFree=1852616/2055920 swapFree=4192956/4192956
[pid=13234] ppid=13232 vsize=5360 CPUtime=0
/proc/13234/stat : 13234 (runpbsmodels) S 13232 13234 13188 0 -1 4194304 286 0 0 0 0 0 0 0 18 0 1 0 7279596 5488640 234 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 243181085508 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/13234/statm: 1340 234 195 169 0 51 0
[pid=13235] ppid=13234 vsize=5360 CPUtime=0
/proc/13235/stat : 13235 (runpbsmodels) D 13234 13234 13188 0 -1 4194368 18 0 0 0 0 0 0 0 18 0 1 0 7279596 5488640 234 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 243181088039 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/13235/statm: 1340 234 195 169 0 51 0

Child status: 0
Real time (s): 0.180062
CPU time (s): 0.196969
CPU user time (s): 0.177972
CPU system time (s): 0.018997
CPU usage (%): 109.39
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node46 on Wed Jun  7 04:00:18 UTC 2006


FILE ID= 45725-1149652818

PBS_JOBID= 324224

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-200-6_0-yes1-4.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node46/45725-1149652818/instance-45725-1149652818.opb 454194854  ROOT/tmp/node46/45725-1149652818
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node46/watcher-45725-1149652818 -o ROOT/results/node46/solver-45725-1149652818 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node46/45725-1149652818/instance-45725-1149652818.opb 454194854  ROOT/tmp/node46/45725-1149652818

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  8cf8fb760748f7e5d9e3b99aa5c9f720

RANDOM SEED= 454194854


/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.216
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.216
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:       1853016 kB
Buffers:         30460 kB
Cached:         113564 kB
SwapCached:          0 kB
Active:         112860 kB
Inactive:        45688 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1853016 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             284 kB
Writeback:           0 kB
Mapped:          24936 kB
Slab:            30416 kB
Committed_AS:    55540 kB
PageTables:       1412 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node46 on Wed Jun  7 04:00:19 UTC 2006