Trace number 85348

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
glpPB 0.2OPT94 43.1994 43.2197

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/primes-dimacs-cnf/normalized-jnh205.opb
MD5SUM337fa63ae90b2f1f31bfc9ba194017c3
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark94
Best CPU time to get the best result obtained on this benchmark0.019996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 94
Optimality of the best value was proved YES
Number of variables200
Total number of constraints900
Number of constraints which are clauses900
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 constraint2
Maximum length of a constraint11
Number of terms in the objective function 200
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 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
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 glpPB 0.2 (July 2006)
0.00	c An Application of GLPK 4.10 for PB Constraints
0.00	c Done @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
43.21	c starting to Solve
43.21	c total time = 43.19
43.21	o 94
43.21	c quality of integer solution is H
43.21	s OPTIMUM FOUND
43.21	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
43.21	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
43.21	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
43.21	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
43.21	v -x116 -x117 x118 x119 -x120 -x121 x122 -x123 -x124 x125 -x126 x127 -x128 x129 -x130 -x131 x132 -x133 x134 -x135 x136 x137 -x138
43.21	v -x139 x140 -x141 x142 -x143 x144 x145 -x146 x147 -x148 x149 -x150 x151 -x152 x153 -x154 x155 -x156 -x157 -x158 -x159 x160 x161
43.21	v -x162 x163 -x164 x165 -x166 -x167 x168 x169 -x170 -x171 -x172 x173 -x174 -x175 x176 x177 -x178 x179 -x180 -x181 x182 x183 -x184
43.21	v x185 -x186 -x187 x188 -x189 x190 x191 -x192 x193 -x194 x195 -x196 -x197 x198 -x199 x200

Verifier Data (download as text)

OK	94

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.3 (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/node24/watcher-85348-1154169698 -o ROOT/results/node24/solver-85348-1154169698 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node24/85348-1154169698/instance-85348-1154169698.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 14316
/proc/meminfo: memFree=1565592/2055920 swapFree=4183196/4192956
[pid=14316] ppid=14314 vsize=2424 CPUtime=0
/proc/14316/stat : 14316 (glpPBv3) R 14314 14316 14267 0 -1 0 148 0 0 0 0 0 0 0 18 0 1 0 163830497 2482176 128 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 2575224 0 0 4096 0 0 0 0 17 1 0 0
/proc/14316/statm: 606 128 109 40 0 11 0

[startup+10.0025 s]
/proc/loadavg: 0.93 0.95 0.90 2/64 14316
/proc/meminfo: memFree=1563808/2055920 swapFree=4183196/4192956
[pid=14316] ppid=14314 vsize=4252 CPUtime=9.99
/proc/14316/stat : 14316 (glpPBv3) R 14314 14316 14267 0 -1 0 702 0 0 0 996 3 0 0 25 0 1 0 163830497 4354048 671 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 134543497 0 0 4096 0 0 0 0 17 1 0 0
/proc/14316/statm: 1063 671 227 40 0 480 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 4252

[startup+20.0084 s]
/proc/loadavg: 0.94 0.96 0.91 2/64 14316
/proc/meminfo: memFree=1563760/2055920 swapFree=4183196/4192956
[pid=14316] ppid=14314 vsize=4252 CPUtime=19.99
/proc/14316/stat : 14316 (glpPBv3) R 14314 14316 14267 0 -1 0 726 0 0 0 1994 5 0 0 25 0 1 0 163830497 4354048 689 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 134585279 0 0 4096 0 0 0 0 17 1 0 0
/proc/14316/statm: 1063 689 227 40 0 480 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 4252

[startup+30.0143 s]
/proc/loadavg: 0.95 0.96 0.91 2/64 14316
/proc/meminfo: memFree=1563632/2055920 swapFree=4183196/4192956
[pid=14316] ppid=14314 vsize=4484 CPUtime=30
/proc/14316/stat : 14316 (glpPBv3) R 14314 14316 14267 0 -1 0 5913 0 0 0 2990 10 0 0 25 0 1 0 163830497 4591616 723 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/14316/statm: 1121 723 227 40 0 538 0
Current children cumulated CPU time (s) 30
Current children cumulated vsize (Kb) 4484

[startup+40.0202 s]
/proc/loadavg: 0.95 0.96 0.91 2/64 14316
/proc/meminfo: memFree=1563568/2055920 swapFree=4183196/4192956
[pid=14316] ppid=14314 vsize=4532 CPUtime=39.99
/proc/14316/stat : 14316 (glpPBv3) R 14314 14316 14267 0 -1 0 14038 0 0 0 3984 15 0 0 25 0 1 0 163830497 4640768 735 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 134640458 0 0 4096 0 0 0 0 17 1 0 0
/proc/14316/statm: 1133 735 227 40 0 550 0
Current children cumulated CPU time (s) 39.99
Current children cumulated vsize (Kb) 4532

Child status: 30
Real time (s): 43.2197
CPU time (s): 43.1994
CPU user time (s): 43.0225
CPU system time (s): 0.176973
CPU usage (%): 99.953
Max. virtual memory (cumulated for all children) (Kb): 4532
The end

Launcher Data (download as text)

Begin job on node24 on Sat Jul 29 10:41:38 UTC 2006


FILE ID= 85348-1154169698

PBS_JOBID= 893122

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-jnh205.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node24/85348-1154169698/instance-85348-1154169698.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-85348-1154169698 -o ROOT/results/node24/solver-85348-1154169698 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node24/85348-1154169698/instance-85348-1154169698.opb

MD5SUM SOLVER= 29ce95346658d7502ba983059bfb8cff
MD5SUM BENCH=  337fa63ae90b2f1f31bfc9ba194017c3

RANDOM SEED= 493793845

TIMEOUT= 1800 seconds


/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.266
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.266
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:       1565864 kB
Buffers:         24560 kB
Cached:         410744 kB
SwapCached:       3500 kB
Active:          86456 kB
Inactive:       357384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1565864 kB
SwapTotal:     4192956 kB
SwapFree:      4183196 kB
Dirty:             276 kB
Writeback:           0 kB
Mapped:          14552 kB
Slab:            32264 kB
Committed_AS:   651660 kB
PageTables:       1468 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node24 on Sat Jul 29 10:42:21 UTC 2006