Trace number 365071

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-clasp 2007-04-10OPT200 0.12698 0.137161

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-200-2_0-yes1-2.opb
MD5SUM2b7ee6a2452febe7d149ef87c021382f
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.018996
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.05/0.09	o 200
0.07/0.13	s OPTIMUM FOUND
0.07/0.13	v x2 x3 x6 x7 x10 x11 x13 x15 x18 x19 x22 x23 x26 x27 x30 x31 x34 x36 x37 x40 x42 x43 x45 x47 x49 x52 x53 x55 x57 x60 x62 x63 x66 x68 x69
0.07/0.13	v x72 x73 x76 x77 x80 x81 x84 x86 x87 x90 x92 x94 x96 x97 x99 x101 x103 x105 x107 x110 x112 x114 x116 x118 x120 x121 x124 x125 x127
0.07/0.13	v x130 x132 x134 x135 x137 x140 x142 x143 x145 x147 x150 x152 x153 x156 x157 x160 x161 x164 x166 x168 x170 x171 x174 x175 x178 x179
0.07/0.13	v x181 x184 x185 x187 x189 x191 x193 x195 x197 x200 x202 x203 x205 x208 x210 x212 x213 x215 x217 x220 x222 x223 x225 x227 x230 x231
0.07/0.13	v x233 x235 x238 x239 x242 x243 x246 x248 x250 x251 x253 x255 x258 x260 x261 x263 x266 x268 x270 x271 x274 x276 x278 x279 x282 x283
0.07/0.13	v x286 x288 x289 x291 x294 x295 x297 x299 x302 x304 x306 x308 x310 x311 x313 x316 x318 x319 x321 x324 x325 x327 x330 x331 x334 x335
0.07/0.13	v x337 x340 x341 x343 x345 x347 x349 x352 x353 x355 x357 x359 x361 x364 x365 x368 x369 x372 x373 x375 x378 x380 x381 x384 x385 x388
0.07/0.13	v x389 x391 x393 x395 x397 x400

Verifier Data (download as text)

OK	200

Conversion Script Data (download as text)

/tmp/evaluation/365071-1177045980/instance-365071-1177045980.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node33/watcher-365071-1177045980 -o ROOT/results/node33/solver-365071-1177045980 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-365071-1177045980.opb /tmp/evaluation/365071-1177045980/temp 

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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.93 0.99 0.99 3/77 9332
/proc/meminfo: memFree=1731696/2055920 swapFree=4180512/4192956
[pid=9332] ppid=9330 vsize=12268 CPUtime=0
/proc/9332/stat : 9332 (pbclasp) R 9330 9332 7673 0 -1 4194304 351 0 0 0 0 0 0 0 18 0 1 0 152513490 12562432 317 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 210833030142 0 0 4224 0 0 0 0 17 1 0 0
/proc/9332/statm: 3067 317 242 3 0 167 0

[startup+0.094779 s]
/proc/loadavg: 0.93 0.99 0.99 3/77 9332
/proc/meminfo: memFree=1731696/2055920 swapFree=4180512/4192956
[pid=9332] ppid=9330 vsize=12532 CPUtime=0.05
/proc/9332/stat : 9332 (pbclasp) S 9330 9332 7673 0 -1 4194304 613 1588 0 0 0 0 4 1 16 0 1 0 152513490 12832768 493 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 210833031060 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/9332/statm: 3133 493 343 3 0 233 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 12532

[startup+0.102781 s]
/proc/loadavg: 0.93 0.99 0.99 3/77 9332
/proc/meminfo: memFree=1731696/2055920 swapFree=4180512/4192956
[pid=9332] ppid=9330 vsize=12532 CPUtime=0.07
/proc/9332/stat : 9332 (pbclasp) S 9330 9332 7673 0 -1 4194304 721 2547 0 0 0 0 6 1 16 0 1 0 152513490 12832768 496 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 210833027170 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/9332/statm: 3133 496 343 3 0 233 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 12532

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

Child status: 0
Real time (s): 0.137161
CPU time (s): 0.12698
CPU user time (s): 0.091986
CPU system time (s): 0.034994
CPU usage (%): 92.5773
Max. virtual memory (cumulated for all children) (KiB): 12532

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.091986
system time used= 0.034994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5216
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= 151
involuntary context switches= 32

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node33 on Fri Apr 20 05:13:00 UTC 2007

IDJOB= 365071
IDBENCH= 2190
IDSOLVER= 167
FILE ID= node33/365071-1177045980

PBS_JOBID= 4640103

Free space on /tmp= 66477 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-200-2_0-yes1-2.opb
COMMAND LINE= pbclasp instance-365071-1177045980.opb /tmp/evaluation/365071-1177045980/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node33/convwatcher-365071-1177045980 -o ROOT/results/node33/conversion-365071-1177045980 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/365071-1177045980/instance-365071-1177045980.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node33/watcher-365071-1177045980 -o ROOT/results/node33/solver-365071-1177045980 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-365071-1177045980.opb /tmp/evaluation/365071-1177045980/temp

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  2b7ee6a2452febe7d149ef87c021382f

RANDOM SEED= 409578621

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node33.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.272
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.272
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:       1732040 kB
Buffers:         38612 kB
Cached:         186708 kB
SwapCached:       2276 kB
Active:         197468 kB
Inactive:        72844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1732040 kB
SwapTotal:     4192956 kB
SwapFree:      4180512 kB
Dirty:             504 kB
Writeback:           0 kB
Mapped:          59952 kB
Slab:            38804 kB
Committed_AS:  1699136 kB
PageTables:       1996 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66477 MiB

End job on node33 on Fri Apr 20 05:13:00 UTC 2007