Trace number 85449

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.2OPT304 0.010997 0.0148861

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/
~walser/benchmarks/course-ass/normalized-ss97-6.opb
MD5SUMdcfce19ac0444148b26b7675e35c76bc
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark304
Best CPU time to get the best result obtained on this benchmark0.010997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 304
Optimality of the best value was proved YES
Number of variables257
Total number of constraints97
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)97
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint44
Number of terms in the objective function 173
Biggest coefficient in the objective function 100
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 8448
Number of bits of the sum of numbers in the objective function 14
Biggest number in a constraint 100
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 8448
Number of bits of the biggest sum of numbers14
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
0.01	c starting to Solve
0.01	c total time = 0
0.01	o 304
0.01	c quality of integer solution is H
0.01	s OPTIMUM FOUND
0.01	v x134 x178 -x218 x4 x180 x8 x9 -x97 x185 -x225 x186 -x226 x11 -x99 -x143 x187 -x227 x100 x13 x14 -x15 x59 x104 x61 -x105 -x149 x230
0.01	v x62 x20 -x108 -x109 x153 x22 -x110 -x154 -x111 x155 x112 x192 -x232 -x27 x71 x237 x118 x198 -x238 x199 -x239 x119 -x200 x240
0.01	v x164 x121 -x202 x242 -x203 x243 x122 -x204 x244 -x124 x168 -x206 x246 x125 x247 x38 -x126 -x170 -x208 x248 x127 x249 x40 -x172
0.01	v x250 -x213 x253 x130 -x214 x254 x131 -x215 x255 x132 -x216 x256 -x133 x257 -x2 -x46 -x90 -x91 -x179 -x48 -x220 -x222 -x224 -x53
0.01	v -x141 -x12 -x56 -x144 -x228 -x57 -x145 -x229 -x58 -x146 -x103 -x147 -x16 -x148 -x18 -x150 x19 -x63 -x107 -x151 -x152 -x66 -x24
0.01	v -x68 -x156 x25 -x69 -x113 -x157 -x191 x231 -x159 -x233 -x234 -x235 -x236 -x30 -x74 -x162 -x31 -x75 -x163 -x76 -x120 -x241 -x33
0.01	v -x77 -x165 -x34 -x166 -x35 -x79 -x245 -x80 -x81 -x169 -x82 -x39 -x83 -x171 -x84 -x128 -x42 -x86 -x174 -x43 -x87 -x175 -x44 -x88
0.01	v -x176 -x177 -x217 x1 -x3 -x5 -x6 -x7 -x10 -x17 -x21 -x23 -x26 -x28 -x29 -x32 -x36 -x37 -x41 -x45 x47 x49 x50 -x51 -x52 -x54 -x55
0.01	v -x60 -x64 -x65 -x67 -x70 -x72 -x73 -x78 -x85 x89 -x92 -x93 -x94 -x95 -x96 -x98 -x101 -x102 -x106 -x114 -x115 -x116 -x117 -x123
0.01	v -x129 -x135 -x136 -x137 -x138 x139 -x140 x142 x158 x160 x161 x167 x173 -x181 x182 -x183 x184 x188 x189 -x190 x193 x194 x195
0.01	v x196 -x197 x201 x205 -x207 -x209 -x210 -x211 -x212 x219 x221 x223 x251 x252

Verifier Data (download as text)

OK	304

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/node44/watcher-85449-1154171722 -o ROOT/results/node44/solver-85449-1154171722 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node44/85449-1154171722/instance-85449-1154171722.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 13282
/proc/meminfo: memFree=1322064/2055920 swapFree=4183124/4192956
[pid=13282] ppid=13280 vsize=2376 CPUtime=0
/proc/13282/stat : 13282 (glpPBv3) R 13280 13282 13233 0 -1 0 186 0 0 0 0 0 0 0 19 0 1 0 164043108 2433024 156 18446744073709551615 134512640 134678228 4294956672 18446744073709551615 11748288 0 0 4096 0 0 0 0 17 1 0 0
/proc/13282/statm: 594 167 145 40 0 11 0

Child status: 30
Real time (s): 0.0148861
CPU time (s): 0.010997
CPU user time (s): 0.008998
CPU system time (s): 0.001999
CPU usage (%): 73.8745
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node44 on Sat Jul 29 11:15:22 UTC 2006


FILE ID= 85449-1154171722

PBS_JOBID= 893223

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/course-ass/normalized-ss97-6.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node44/85449-1154171722/instance-85449-1154171722.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node44/watcher-85449-1154171722 -o ROOT/results/node44/solver-85449-1154171722 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/glpPBv3 ROOT/tmp/node44/85449-1154171722/instance-85449-1154171722.opb

MD5SUM SOLVER= 29ce95346658d7502ba983059bfb8cff
MD5SUM BENCH=  dcfce19ac0444148b26b7675e35c76bc

RANDOM SEED= 562215208

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.238
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.238
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:       1322272 kB
Buffers:         38328 kB
Cached:         619388 kB
SwapCached:       3516 kB
Active:         231068 kB
Inactive:       435092 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1322272 kB
SwapTotal:     4192956 kB
SwapFree:      4183124 kB
Dirty:             320 kB
Writeback:           0 kB
Mapped:          14476 kB
Slab:            53488 kB
Committed_AS:   710172 kB
PageTables:       1408 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node44 on Sat Jul 29 11:15:22 UTC 2006