Trace number 2684435

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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/CT 0.1OPT24774 0.087986 0.0897679

General information on the benchmark

Name/OPT-BIGINT-LIN/leberre/opb-trendy/misc2010/
datasets/caixa/normalized-1097.cudf.trendy.opb
MD5SUM607e72b1162859b296603278329a18bd
Bench CategoryOPT-BIGINT-LIN (optimisation, big integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark24774
Best CPU time to get the best result obtained on this benchmark0.062989
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables484
Total number of constraints2343
Number of constraints which are clauses2343
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 constraint1
Maximum length of a constraint3
Number of terms in the objective function 310
Biggest coefficient in the objective function 24649
Number of bits for the biggest coefficient in the objective function 15
Sum of the numbers in the objective function 3820750
Number of bits of the sum of numbers in the objective function 22
Biggest number in a constraint 24649
Number of bits of the biggest number in a constraint 15
Biggest sum of numbers in a constraint 3820750
Number of bits of the biggest sum of numbers22
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 

0.00/0.00	c PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.01/0.02	c constraints 0/0 clauses 2052/0 units 140
0.01/0.02	c vars 484
0.01/0.02	c objective 238 + 0
0.01/0.06	c 0.06099 7.61328 1 38
0.01/0.06	o 123370
0.01/0.06	c 0.06199 7.93359 3 145
0.01/0.06	o 98721
0.01/0.06	c 0.06299 7.93359 14 269
0.01/0.06	o 74072
0.01/0.07	c 0.06399 7.93359 22 352
0.01/0.07	o 49423
0.01/0.07	c 0.065989 7.93359 26 424
0.01/0.07	o 24774
0.01/0.07	c 0.066989 7.93359 26 424
0.01/0.07	s OPTIMUM FOUND
0.01/0.07	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 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 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 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 x116 x117 x118 -x119 x120 -x121 x122 x123 x124 x125 x126 -x127 x128 x129 x130 x131 x132 x133 x134 x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 x166 x167 x168 x169 x170 x171 x172 x173 x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189 -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 -x210 -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x230 -x231 -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239 -x240 -x241 -x242 -x243 -x244 -x245 -x246 -x247 -x248 -x249 -x250 -x251 -x252 -x253 -x254 -x255 -x256 -x257 -x258 -x259 -x260 -x261 -x262 -x263 -x264 -x265 -x266 -x267 -x268 -x269 -x270 -x271 -x272 x273 -x274 -x275 -x276 -x277 -x278 -x279 -x280 -x281 -x282 -x283 -x284 -x285 -x286 -x287 -x288 -x289 -x290 -x291 -x292 -x293 -x294 -x295 -x296 -x297 -x298 -x299 -x300 -x301 -x302 -x303 -x304 -x305 -x306 -x307 -x308 -x309 -x310 -x311 -x312 -x313 -x314 -x315 -x316 -x317 -x318 -x319 -x320 -x321 -x322 -x323 -x324 -x325 -x326 -x327 -x328 -x329 x330 x331 x332 x333 x334 x335 x336 x337 x338 x339 x340 x341 x342 x343 x344 x345 x346 x347 x348 x349 x350 x351 x352 x353 x354 x355 x356 x357 x358 x359 x360 x361 x362 x363 x364 x365 x366 x367 x368 x369 x370 x371 x372 x373 x374 x375 x376 x377 x378 x379 x380 x381 x382 x383 x384 x385 x386 x387 x388 x389 x390 x391 x392 x393 x394 x395 x396 x397 x398 x399 x400 x401 x402 x403 x404 x405 x406 x407 x408 x409 x410 x411 x412 x413 x414 x415 x416 x417 x418 x419 x420 x421 x422 x423 x424 x425 x426 x427 x428 x429 x430 x431 -x432 -x433 -x434 -x435 -x436 -x437 -x438 -x439 -x440 -x441 -x442 -x443 -x444 -x445 -x446 -x447 -x448 -x449 -x450 -x451 -x452 -x453 -x454 -x455 -x456 -x457 -x458 -x459 -x460 x461 -x462 x463 x464 x465 x466 x467 x468 x469 x470 x471 x472 x473 x474 x475 x476 x477 x478 x479 x480 x481 x482 x483 x484

Verifier Data 

OK	24774

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2684435-1277516154/watcher-2684435-1277516154 -o /tmp/evaluation-result-2684435-1277516154/solver-2684435-1277516154 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2684435-1277516154.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.32 1.11 1.03 3/106 1398
/proc/meminfo: memFree=1810612/2059040 swapFree=4135556/4192956
[pid=1398] ppid=1396 vsize=2208 CPUtime=0
/proc/1398/stat : 1398 (pbct) R 1396 1398 32179 0 -1 4202496 258 0 0 0 0 0 0 0 20 0 1 0 127219414 2260992 180 1992294400 134512640 136485738 4287562432 18446744073709551615 135350462 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/1398/statm: 552 180 156 482 0 68 0

[startup+0.018134 s]
/proc/loadavg: 1.32 1.11 1.03 3/106 1398
/proc/meminfo: memFree=1810612/2059040 swapFree=4135556/4192956
[pid=1398] ppid=1396 vsize=2208 CPUtime=0.01
/proc/1398/stat : 1398 (pbct) R 1396 1398 32179 0 -1 4202496 272 0 0 0 1 0 0 0 20 0 1 0 127219414 2260992 194 1992294400 134512640 136485738 4287562432 18446744073709551615 135178790 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/1398/statm: 552 194 157 482 0 68 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 2208

Solver just ended. Dumping a history of the last processes samples

[startup+0.018134 s]
/proc/loadavg: 1.32 1.11 1.03 3/106 1398
/proc/meminfo: memFree=1810612/2059040 swapFree=4135556/4192956
[pid=1398] ppid=1396 vsize=2208 CPUtime=0.01
/proc/1398/stat : 1398 (pbct) R 1396 1398 32179 0 -1 4202496 272 0 0 0 1 0 0 0 20 0 1 0 127219414 2260992 194 1992294400 134512640 136485738 4287562432 18446744073709551615 135178790 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/1398/statm: 552 194 157 482 0 68 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 2208

Child status: 0
Real time (s): 0.0897679
CPU time (s): 0.087986
CPU user time (s): 0.081987
CPU system time (s): 0.005999
CPU usage (%): 98.0149
Max. virtual memory (cumulated for all children) (KiB): 2208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.081987
system time used= 0.005999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1724
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 2
involuntary context switches= 17

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node001 at 2010-06-26 03:35:54
IDJOB=2684435
IDBENCH=72442
IDSOLVER=1170
FILE ID=node001/2684435-1277516154
PBS_JOBID= 11190640
Free space on /tmp= 62440 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB10/normalized-PB10/OPT-BIGINT-LIN/leberre/opb-trendy/misc2010/datasets/caixa/normalized-1097.cudf.trendy.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2684435-1277516154/watcher-2684435-1277516154 -o /tmp/evaluation-result-2684435-1277516154/solver-2684435-1277516154 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2684435-1277516154.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 607e72b1162859b296603278329a18bd
RANDOM SEED=172209159

node001.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.202
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.40
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.202
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1811016 kB
Buffers:         36360 kB
Cached:         113116 kB
SwapCached:       9820 kB
Active:          44772 kB
Inactive:       117916 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1811016 kB
SwapTotal:     4192956 kB
SwapFree:      4135556 kB
Dirty:            2604 kB
Writeback:           0 kB
AnonPages:       11636 kB
Mapped:           8428 kB
Slab:            63404 kB
PageTables:       4196 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183088 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62440 MiB
End job on node001 at 2010-06-26 03:35:54