Trace number 40355

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
bsolo 2006/05OPT200 0.043992 0.056282

General information on the benchmark

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

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node39/watcher-40355-1149415689 -o ROOT/results/node39/solver-40355-1149415689 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node39/40355-1149415689/instance-40355-1149415689.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.71 0.91 0.93 3/64 27976
/proc/meminfo: memFree=1861752/2055920 swapFree=4180844/4192956
[pid=27976] ppid=27974 vsize=4664 CPUtime=0
/proc/27976/stat : 27976 (bsolo) R 27974 27976 27930 0 -1 0 119 0 0 0 0 0 0 0 19 0 1 0 207235219 4775936 101 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 11096152 0 0 4096 0 0 0 0 17 1 0 0
/proc/27976/statm: 1166 109 90 55 0 46 0

Child status: 30
Real time (s): 0.056282
CPU time (s): 0.043992
CPU user time (s): 0.035994
CPU system time (s): 0.007998
CPU usage (%): 78.1635
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node39 on Sun Jun  4 10:08:09 UTC 2006


FILE ID= 40355-1149415689

PBS_JOBID= 315225

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-200-2_0-yes1-1.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node39/40355-1149415689/instance-40355-1149415689.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-40355-1149415689 -o ROOT/results/node39/solver-40355-1149415689 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node39/40355-1149415689/instance-40355-1149415689.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  2014a0d713a146a668fdb58f2d1d22f3

RANDOM SEED= 555504280


/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.213
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	: 5931.00
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.213
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:       1862152 kB
Buffers:         12868 kB
Cached:         119848 kB
SwapCached:       3624 kB
Active:          38348 kB
Inactive:       102956 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1862152 kB
SwapTotal:     4192956 kB
SwapFree:      4180844 kB
Dirty:             332 kB
Writeback:           0 kB
Mapped:          14596 kB
Slab:            38476 kB
Committed_AS:   424312 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node39 on Sun Jun  4 10:08:09 UTC 2006