Trace number 49029

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.31OPT41 0.06199 0.071369

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=41-Q=347.opb
MD5SUM557ed9c7351bf94baf7c04ddf6f2d025
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark41
Best CPU time to get the best result obtained on this benchmark0.005998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 41
Optimality of the best value was proved YES
Number of variables99
Total number of constraints244
Number of constraints which are clauses243
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 constraint81
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 65536
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 275348
Number of bits of the biggest sum of numbers19
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.06	o 41
0.06	s OPTIMUM FOUND
0.06	v x1 x4 x6 x19 x10 x20 x11 x22 x13 x23 x14 x25 x16 x27 x18 x46 x47 x49 x50 x52 x54 x64 x65 x67 x68 x70 x72 -x2 -x3 -x5 -x7 -x8 -x9 -x21 -x12
0.06	v -x24 -x15 -x26 -x17 -x28 -x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x48 -x51 -x53 -x55
0.06	v -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x66 -x69 -x71 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87
0.06	v -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99

Verifier Data (download as text)

OK	41

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/node68/watcher-49029-1149845161 -o ROOT/results/node68/solver-49029-1149845161 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node68/49029-1149845161/instance-49029-1149845161.opb 84662411 ROOT/tmp/node68/49029-1149845161 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.58 0.76 0.83 3/64 32454
/proc/meminfo: memFree=1640064/2055920 swapFree=4182328/4192956
[pid=32454] ppid=32452 vsize=5360 CPUtime=0
/proc/32454/stat : 32454 (runpbsmodels) S 32452 32454 32408 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 250185616 5488640 234 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 257414456132 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/32454/statm: 1340 234 195 169 0 51 0
[pid=32455] ppid=32454 vsize=8540 CPUtime=0
/proc/32455/stat : 32455 (pbsmodels-v1.31) R 32454 32454 32408 0 -1 4194304 73 0 0 0 0 0 0 0 20 0 1 0 250185616 8744960 55 18446744073709551615 4194304 4206940 548682069040 18446744073709551615 257411839369 0 0 4096 0 0 0 0 17 1 0 0
/proc/32455/statm: 2135 55 41 3 0 55 0

Child status: 0
Real time (s): 0.071369
CPU time (s): 0.06199
CPU user time (s): 0.042993
CPU system time (s): 0.018997
CPU usage (%): 86.8584
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node68 on Fri Jun  9 09:26:01 UTC 2006


FILE ID= 49029-1149845161

PBS_JOBID= 382389

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=41-Q=347.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node68/49029-1149845161/instance-49029-1149845161.opb 84662411  ROOT/tmp/node68/49029-1149845161
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node68/watcher-49029-1149845161 -o ROOT/results/node68/solver-49029-1149845161 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node68/49029-1149845161/instance-49029-1149845161.opb 84662411  ROOT/tmp/node68/49029-1149845161

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  557ed9c7351bf94baf7c04ddf6f2d025

RANDOM SEED= 84662411


/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.279
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.279
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:       1640272 kB
Buffers:         41072 kB
Cached:         299672 kB
SwapCached:       2384 kB
Active:         112224 kB
Inactive:       237292 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1640272 kB
SwapTotal:     4192956 kB
SwapFree:      4182328 kB
Dirty:             176 kB
Writeback:           0 kB
Mapped:          15560 kB
Slab:            52164 kB
Committed_AS:   536272 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node68 on Fri Jun  9 09:26:01 UTC 2006