Trace number 37467

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
Pueblo 1.3OPT10447498 0.05699 0.058761

General information on the benchmark

Namenormalized-PB06/OPT-MEDINT/mps-v2-20-10/MIPLIB/
miplib/normalized-mps-v2-20-10-p0291.opb
MD5SUM5dbbb39821171ddf7cf17b36f56beeda
Bench CategoryOPT-MEDINT (optimisation, medium integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark10447498
Best CPU time to get the best result obtained on this benchmark0.05699
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 10447498
Optimality of the best value was proved YES
Number of variables290
Total number of constraints205
Number of constraints which are clauses189
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints14
Minimum length of a constraint2
Maximum length of a constraint53
Number of terms in the objective function 288
Biggest coefficient in the objective function 80000000
Number of bits for the biggest coefficient in the objective function 27
Sum of the numbers in the objective function 686402651
Number of bits of the sum of numbers in the objective function 30
Biggest number in a constraint 80000000
Number of bits of the biggest number in a constraint 27
Biggest sum of numbers in a constraint 686402651
Number of bits of the biggest sum of numbers30
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 Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.01	c starting to Solve
0.01	c #variables read: 290 - #constraints read: 206
0.01	o 172780597
0.01	o 172502672
0.01	o 169406572
0.01	o 134103755
0.01	o 133767027
0.01	o 132110745
0.01	o 131948852
0.01	o 130466595
0.01	o 126025913
0.01	o 118408337
0.01	o 116479620
0.01	o 82814826
0.01	o 80490409
0.01	o 70266191
0.01	o 69040216
0.01	o 68180247
0.01	o 66055675
0.01	o 64126958
0.01	o 63185550
0.01	o 63133600
0.01	o 61204883
0.01	o 32755511
0.02	o 32382101
0.02	o 31385578
0.02	o 30338931
0.02	o 28410214
0.02	o 27016856
0.02	o 26564906
0.02	o 25488139
0.02	o 24410214
0.02	o 18349242
0.02	o 18244003
0.02	o 17302595
0.02	o 15373878
0.02	o 15357896
0.02	o 15173878
0.02	o 14131921
0.03	o 13469978
0.03	o 13018028
0.03	o 12792053
0.03	o 12392053
0.03	o 12166078
0.03	o 11879425
0.03	o 11830693
0.03	o 11604718
0.04	o 11378743
0.04	o 11325773
0.04	o 10970615
0.04	o 10919075
0.04	o 10796590
0.04	o 10745050
0.05	o 10711913
0.05	o 10699150
0.05	o 10589428
0.05	o 10537888
0.05	c optimum objective found = 10537888
0.05	c total time              : 0.05 s
0.05	s OPTIMUM FOUND
0.05	v -x18 -x19 -x21 -x22 -x30 -x31 -x33 -x34 -x41 -x42 -x44 x45 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64
0.05	v -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
0.05	v -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 -x109 -x110 -x111 -x112
0.05	v -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x129 x130 -x131 -x132 -x133
0.05	v -x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x145 -x146 -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155
0.05	v -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176
0.05	v -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189 -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197
0.05	v -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 -x210 -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218
0.05	v -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x230 -x231 -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239
0.05	v -x240 -x241 x242 x243 -x244 -x245 -x246 -x247 -x248 -x249 x250 -x251 x252 x253 -x254 -x255 -x256 -x257 -x258 -x1 -x20 -x32
0.05	v -x43 -x2 -x3 -x4 x5 x6 -x23 -x35 -x46 -x7 -x24 x36 -x25 -x37 -x26 -x38 -x47 -x8 -x27 -x39 -x48 -x10 -x11 -x28 x49 -x29 -x40 -x50
0.05	v -x12 -x13 -x14 -x15 -x16 -x17 -x260 -x274 -x280 x286 -x262 x263 x265 -x259 -x273 -x279 -x285 -x261 -x264 x266 -x275 -x281 -x287
0.05	v -x267 -x276 -x282 -x288 -x268 -x277 -x283 -x289 -x269 -x270 -x278 -x284 -x290 -x271 -x272 -x9 -x144

Verifier Data (download as text)

OK	10447498

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/node36/watcher-37467-1149244213 -o ROOT/results/node36/solver-37467-1149244213 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node36/37467-1149244213/instance-37467-1149244213.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 1/64 22849
/proc/meminfo: memFree=1588216/2055920 swapFree=4181452/4192956
[pid=22849] ppid=22847 vsize=2572 CPUtime=0
/proc/22849/stat : 22849 (Pueblo13) R 22847 22849 22803 0 -1 4194304 270 0 0 0 0 0 0 0 19 0 1 0 190087422 2633728 241 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 1963643 0 0 4096 0 0 0 0 17 0 0 0
/proc/22849/statm: 643 241 199 16 0 84 0

Child status: 30
Real time (s): 0.058761
CPU time (s): 0.05699
CPU user time (s): 0.052991
CPU system time (s): 0.003999
CPU usage (%): 96.9861
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node36 on Fri Jun  2 10:30:13 UTC 2006


FILE ID= 37467-1149244213

PBS_JOBID= 297655

BENCH NAME= ROOT/tmp/node36/37467-1149244213/instance-37467-1149244213.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node36/37467-1149244213/instance-37467-1149244213.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node36/watcher-37467-1149244213 -o ROOT/results/node36/solver-37467-1149244213 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node36/37467-1149244213/instance-37467-1149244213.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  5dbbb39821171ddf7cf17b36f56beeda

RANDOM SEED= 754744425


/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.284
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.284
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:       1588424 kB
Buffers:         21260 kB
Cached:         373912 kB
SwapCached:       3444 kB
Active:          42728 kB
Inactive:       361372 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1588424 kB
SwapTotal:     4192956 kB
SwapFree:      4181452 kB
Dirty:             156 kB
Writeback:           0 kB
Mapped:          14916 kB
Slab:            49460 kB
Committed_AS:   213392 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node36 on Fri Jun  2 10:30:13 UTC 2006