Trace number 46616

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
PBS 4.1LOPT34 11.3293 11.3409

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_8.opb
MD5SUM6d3802f2f17c83a21ccf6c0752b41678
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark34
Best CPU time to get the best result obtained on this benchmark11.3293
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 variables392
Total number of constraints679
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints679
Minimum length of a constraint14
Maximum length of a constraint29
Number of terms in the objective function 7
Biggest coefficient in the objective function 64
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 127
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 128
Number of bits of the biggest number in a constraint 8
Biggest sum of numbers in a constraint 635
Number of bits of the biggest sum of numbers10
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00	c PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00	c Solving ROOT/tmp/node80/46616-1149789631/instance-46616-1149789631.opb ......
0.04	c done parsing opb.
0.04	o 62
0.24	o 60
0.27	o 53
0.29	o 52
0.32	o 51
0.52	o 50
0.58	o 49
0.72	o 47
1.06	o 46
1.15	o 45
1.29	o 44
1.53	o 43
1.74	o 42
2.16	o 40
2.37	o 39
2.60	o 37
2.66	o 36
3.67	o 35
3.88	o 34
11.33	o 34
11.33	s OPTIMUM FOUND
11.33	c Total Run Time					11.2913
11.33	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
11.33	v 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
11.33	v 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
11.33	v -x168 x169 -x17 x170 -x171 x172 x173 -x174 -x175 -x176 x177 x178 x179 -x18 x180 x181 x182 x183 x184 -x185 -x186 -x187 -x188
11.33	v -x189 -x19 x190 x191 -x192 -x193 -x194 -x195 -x196 x197 x198 x199 x2 -x20 x200 x201 x202 x203 x204 x205 x206 x207 x208 x209 -x21
11.33	v x210 x211 x212 x213 x214 x215 x216 x217 x218 x219 -x22 x220 x221 x222 x223 x224 x225 x226 x227 x228 x229 -x23 x230 x231 x232 x233
11.33	v x234 x235 x236 -x237 x238 x239 x24 x240 x241 x242 x243 x244 x245 -x246 x247 x248 x249 -x25 -x250 x251 x252 x253 x254 -x255 x256
11.33	v x257 x258 x259 -x26 x260 x261 -x262 x263 x264 -x265 x266 x267 -x268 -x269 -x27 -x270 x271 x272 x273 x274 x275 x276 -x277 -x278
11.33	v -x279 -x28 -x280 -x281 x282 -x283 -x284 -x285 -x286 -x287 x288 x289 x29 x290 x291 x292 x293 x294 x295 x296 x297 x298 x299 -x3
11.33	v -x30 x300 x301 -x302 x303 x304 x305 x306 -x307 x308 x309 -x31 x310 -x311 x312 x313 x314 x315 -x316 x317 x318 x319 x32 -x320 x321
11.33	v x322 -x323 x324 x325 -x326 -x327 -x328 x329 -x33 x330 x331 x332 -x333 -x334 -x335 -x336 -x337 -x338 -x339 -x34 -x340 -x341
11.33	v -x342 x343 x344 x345 x346 x347 x348 x349 -x35 x350 x351 -x352 x353 x354 x355 -x356 x357 x358 -x359 x36 x360 -x361 x362 x363 -x364
11.33	v x365 -x366 -x367 -x368 -x369 x37 -x370 -x371 -x372 x373 x374 x375 x376 x377 -x378 x379 x38 x380 -x381 -x382 -x383 -x384 -x385
11.33	v -x386 x387 x388 -x389 x39 -x390 -x391 -x392 -x4 -x40 -x41 -x42 -x43 x44 x45 -x46 x47 -x48 -x49 -x5 -x50 -x51 -x52 -x53 -x54 x55
11.33	v -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
11.33	v x87 x88 x89 -x9 x90 x91 x92 x93 x94 x95 x96 x97 x98 x99

Verifier Data (download as text)

OK	34

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/node80/watcher-46616-1149789631 -o ROOT/results/node80/solver-46616-1149789631 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node80/46616-1149789631/instance-46616-1149789631.opb 108731625 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.99 0.97 0.91 2/67 13562
/proc/meminfo: memFree=1827152/2055888 swapFree=4085444/4096564
[pid=13562] ppid=13560 vsize=1364 CPUtime=0
/proc/13562/stat : 13562 (PBS4L) R 13560 13562 13516 0 -1 4194304 88 0 0 0 0 0 0 0 19 0 1 0 244601619 1396736 73 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 134602160 0 0 4096 0 0 0 0 17 1 0 0
/proc/13562/statm: 341 86 76 232 0 106 0

[startup+10.003 s]
/proc/loadavg: 0.99 0.97 0.91 2/67 13562
/proc/meminfo: memFree=1821136/2055888 swapFree=4085444/4096564
[pid=13562] ppid=13560 vsize=7672 CPUtime=9.99
/proc/13562/stat : 13562 (PBS4L) R 13560 13562 13516 0 -1 4194304 1758 0 0 0 996 3 0 0 25 0 1 0 244601619 7856128 1587 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135140097 0 0 4096 0 0 0 0 17 1 0 0
/proc/13562/statm: 1918 1587 107 232 0 1683 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 7672

Child status: 0
Real time (s): 11.3409
CPU time (s): 11.3293
CPU user time (s): 11.2963
CPU system time (s): 0.032994
CPU usage (%): 99.8973
Max. virtual memory (cumulated for all children) (Kb): 7672
The end

Launcher Data (download as text)

Begin job on node80 on Thu Jun  8 18:00:31 UTC 2006


FILE ID= 46616-1149789631

PBS_JOBID= 373252

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/golomb-rulers/normalized-OGR_8.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node80/46616-1149789631/instance-46616-1149789631.opb 108731625
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node80/watcher-46616-1149789631 -o ROOT/results/node80/solver-46616-1149789631 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node80/46616-1149789631/instance-46616-1149789631.opb 108731625

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  6d3802f2f17c83a21ccf6c0752b41678

RANDOM SEED= 108731625


/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.264
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	: 6006.16
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.264
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1827360 kB
Buffers:         22596 kB
Cached:         148572 kB
SwapCached:       2436 kB
Active:          37568 kB
Inactive:       142436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1827360 kB
SwapTotal:     4096564 kB
SwapFree:      4085444 kB
Dirty:             160 kB
Writeback:           0 kB
Mapped:          16644 kB
Slab:            35220 kB
Committed_AS:   480636 kB
PageTables:       1276 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node80 on Thu Jun  8 18:00:42 UTC 2006