Trace number 40106

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
bsolo 2006/05OPT1523 9.61654 9.64049

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/
MIPLIB/miplib/normalized-mps-v2-20-10-p0201.opb
MD5SUM303eaeab4b7ccd67c7fab31d13d20bc2
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark1523
Best CPU time to get the best result obtained on this benchmark2.65859
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 1523
Optimality of the best value was proved YES
Number of variables201
Total number of constraints133
Number of constraints which are clauses20
Number of constraints which are cardinality constraints (but not clauses)26
Number of constraints which are nor clauses,nor cardinality constraints87
Minimum length of a constraint3
Maximum length of a constraint67
Number of terms in the objective function 201
Biggest coefficient in the objective function 1920
Number of bits for the biggest coefficient in the objective function 11
Sum of the numbers in the objective function 19980
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 1920
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 19980
Number of bits of the biggest sum of numbers15
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 Time Limit set via PBTIMEOUT to 1800
0.01	c INFO: OSL Context initialized.
0.02	c Initial problem consists of 201 variables and 133 constraints.
0.02	c Switching on LPR.
0.02	c No problem reductions applied in OPT. instance.
0.02	c	preprocess terminated. Elapsed time: 0.012
0.02	c After prepocess the problem consists of 195 variables and 133 constraints.
0.05	c Initial Lower Bound: 1393
0.13	o 2150
0.13	c NEW SOLUTION FOUND: 2150 @ 0.122
0.15	o 2140
0.15	c NEW SOLUTION FOUND: 2140 @ 0.139
0.16	o 2120
0.16	c NEW SOLUTION FOUND: 2120 @ 0.148
0.18	o 2080
0.18	c NEW SOLUTION FOUND: 2080 @ 0.169
0.20	o 2075
0.20	c NEW SOLUTION FOUND: 2075 @ 0.182
0.20	o 2015
0.20	c NEW SOLUTION FOUND: 2015 @ 0.192
0.21	o 2010
0.21	c NEW SOLUTION FOUND: 2010 @ 0.196
0.21	o 1955
0.21	c NEW SOLUTION FOUND: 1955 @ 0.199
0.24	o 1915
0.24	c NEW SOLUTION FOUND: 1915 @ 0.229
0.24	o 1885
0.24	c NEW SOLUTION FOUND: 1885 @ 0.23
0.26	o 1865
0.26	c NEW SOLUTION FOUND: 1865 @ 0.251
0.31	o 1845
0.31	c NEW SOLUTION FOUND: 1845 @ 0.296
0.31	o 1825
0.31	c NEW SOLUTION FOUND: 1825 @ 0.301
0.37	o 1798
0.37	c NEW SOLUTION FOUND: 1798 @ 0.358
0.38	o 1778
0.38	c NEW SOLUTION FOUND: 1778 @ 0.365
0.42	o 1753
0.42	c NEW SOLUTION FOUND: 1753 @ 0.411
0.44	o 1743
0.44	c NEW SOLUTION FOUND: 1743 @ 0.429
0.46	o 1723
0.46	c NEW SOLUTION FOUND: 1723 @ 0.447
0.51	o 1713
0.51	c NEW SOLUTION FOUND: 1713 @ 0.493
0.56	o 1705
0.56	c NEW SOLUTION FOUND: 1705 @ 0.552
0.57	o 1685
0.57	c NEW SOLUTION FOUND: 1685 @ 0.556
0.58	o 1619
0.58	c NEW SOLUTION FOUND: 1619 @ 0.564
0.64	o 1609
0.64	c NEW SOLUTION FOUND: 1609 @ 0.631
0.72	o 1607
0.72	c NEW SOLUTION FOUND: 1607 @ 0.712
0.73	o 1587
0.73	c NEW SOLUTION FOUND: 1587 @ 0.719
0.79	o 1584
0.79	c NEW SOLUTION FOUND: 1584 @ 0.781
0.83	o 1571
0.83	c NEW SOLUTION FOUND: 1571 @ 0.818
1.14	c Sol. found (all assignments made)...
1.14	o 1561
1.14	c NEW SOLUTION FOUND: 1561 @ 1.129
1.35	o 1551
1.35	c NEW SOLUTION FOUND: 1551 @ 1.337
1.58	o 1543
1.58	c NEW SOLUTION FOUND: 1543 @ 1.564
1.59	c Sol. found (all assignments made)...
1.59	o 1533
1.59	c NEW SOLUTION FOUND: 1533 @ 1.582
1.60	c Sol. found (all assignments made)...
1.60	o 1523
1.60	c NEW SOLUTION FOUND: 1523 @ 1.582
3.09	c Restart #1 #Var: 193 LB: 1405 @ 3.074
6.11	c Restart #2 #Var: 190 LB: 1419 @ 6.1
9.63	s OPTIMUM FOUND
9.63	c Cost: 1523
9.63	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
9.63	v -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
9.63	v -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
9.63	v -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
9.63	v -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 x120 -x121 -x122 -x123 -x124 x125 -x126 -x127
9.63	v -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 x138 -x139 x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148
9.63	v -x149 -x150 -x151 -x152 -x153 -x154 -x155 x156 x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169
9.63	v -x170 -x171 -x172 -x173 x174 -x175 -x176 -x177 x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189 -x190
9.63	v -x191 x192 -x193 -x194 -x195 -x196 x197 -x198 -x199 -x200 -x201
9.63	c Exit Code: 30
9.63	c Total time: 9.613 s

Verifier Data (download as text)

OK	1523

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node76/watcher-40106-1149368573 -o ROOT/results/node76/solver-40106-1149368573 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node76/40106-1149368573/instance-40106-1149368573.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.98 3/68 1389
/proc/meminfo: memFree=1405832/2055888 swapFree=4085384/4096564
[pid=1389] ppid=1387 vsize=3440 CPUtime=0
/proc/1389/stat : 1389 (bsolo) R 1387 1389 1343 0 -1 0 66 0 0 0 0 0 0 0 19 0 1 0 202496678 3522560 49 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4779289 0 0 4096 0 0 0 0 17 1 0 0
/proc/1389/statm: 1158 51 37 55 0 42 0

Child status: 30
Real time (s): 9.64049
CPU time (s): 9.61654
CPU user time (s): 9.46356
CPU system time (s): 0.152976
CPU usage (%): 99.7515
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node76 on Sat Jun  3 21:02:53 UTC 2006


FILE ID= 40106-1149368573

PBS_JOBID= 311983

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-p0201.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node76/40106-1149368573/instance-40106-1149368573.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-40106-1149368573 -o ROOT/results/node76/solver-40106-1149368573 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node76/40106-1149368573/instance-40106-1149368573.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  303eaeab4b7ccd67c7fab31d13d20bc2

RANDOM SEED= 27994627


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1406040 kB
Buffers:         36592 kB
Cached:         545484 kB
SwapCached:       2316 kB
Active:          52576 kB
Inactive:       538120 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1406040 kB
SwapTotal:     4096564 kB
SwapFree:      4085384 kB
Dirty:             144 kB
Writeback:           0 kB
Mapped:          16488 kB
Slab:            45760 kB
Committed_AS:   385668 kB
PageTables:       1260 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node76 on Sat Jun  3 21:03:03 UTC 2006