Trace number 365252

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.2OPT3 0.38994 0.394152

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/
benchmarks/radar/normalized-10:10:4.5:0.5:100.opb
MD5SUM4dfe0aab63c58302cf08520fc713ceae
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
Best CPU time to get the best result obtained on this benchmark0.039993
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3
Optimality of the best value was proved YES
Number of variables372
Total number of constraints421
Number of constraints which are clauses345
Number of constraints which are cardinality constraints (but not clauses)76
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint18
Number of terms in the objective function 372
Biggest coefficient in the objective function 220
Number of bits for the biggest coefficient in the objective function 8
Sum of the numbers in the objective function 983
Number of bits of the sum of numbers in the objective function 10
Biggest number in a constraint 220
Number of bits of the biggest number in a constraint 8
Biggest sum of numbers in a constraint 983
Number of bits of the biggest sum of numbers10
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/0.00	c glpPB 0.2 (July 2006)
0.00/0.00	c An Application of GLPK 4.10 for PB Constraints
0.00/0.00	c Done @ University of Michigan, Ann Arbor, MI
0.00/0.00	c  by Hossein Sheini
0.29/0.39	c starting to Solve
0.29/0.39	c total time = 0.38
0.29/0.39	o 3
0.29/0.39	c quality of integer solution is H
0.29/0.39	s OPTIMUM FOUND
0.29/0.39	v -x288 x230 x149 x113 -x98 -x76 -x46 -x24 -x286 -x271 x234 x148 x129 -x114 -x45 -x29 -x270 x233 -x197 x150 x128 -x118 -x99 -x80
0.29/0.39	v -x47 -x28 -x3 -x287 -x272 x254 x235 -x196 -x167 x153 -x134 -x116 -x100 -x78 -x48 -x8 -x292 -x273 x253 -x239 -x198 x166 x152
0.29/0.39	v -x133 -x117 -x103 -x55 -x31 -x7 -x344 x274 -x238 x201 -x172 -x157 -x135 -x101 -x79 -x49 -x32 x343 -x281 x255 -x236 x200 -x171
0.29/0.39	v -x156 -x139 -x102 -x83 -x50 -x35 -x10 x345 x275 x257 -x237 -x204 -x173 -x154 -x138 -x51 -x33 -x11 x346 x276 -x202 -x174 -x155
0.29/0.39	v -x136 -x34 -x12 x347 x277 x258 -x203 -x175 -x137 -x13 -x306 -x289 x115 -x95 -x75 -x310 x229 -x119 -x97 -x23 -x293 x231 -x96
0.29/0.39	v -x81 -x58 -x25 -x291 -x249 x232 x151 x130 -x104 -x59 -x30 -x2 -x284 x248 -x243 -x165 x131 -x84 -x54 -x27 -x4 -x285 -x199 x168
0.29/0.39	v -x161 x132 -x82 -x36 -x9 -x280 x256 -x222 -x212 x169 -x160 -x143 -x52 -x6 x259 -x208 x170 -x14 x350 -x278 x260 -x207 -x189 x179
0.29/0.39	v x351 x261 -x193 -x305 x290 -x127 -x73 -x57 -x309 -x294 -x123 -x94 -x77 -x56 -x283 x246 -x162 -x122 -x112 x74 -x282 x247 -x164
0.29/0.39	v -x108 x85 -x26 x361 -x242 -x218 -x209 -x146 -x107 -x44 x250 -x211 x147 -x40 -x5 x349 x251 -x240 -x221 x182 -x158 -x142 -x53
0.29/0.39	v -x39 -x22 x348 x252 x183 -x18 -x279 x265 -x205 -x188 x178 -x159 -x140 -x17 -x192 x307 x302 x245 -x126 -x109 -x311 x298 x244
0.29/0.39	v -x163 -x111 -x72 x357 -x297 -x145 -x120 x93 -x41 -x210 -x144 x89 -x43 x360 -x313 -x217 -x181 -x121 -x105 x88 -x65 -x19 -x314
0.29/0.39	v x180 -x21 -x268 -x241 x223 -x106 -x37 x269 -x337 x264 -x206 -x190 x176 -x141 -x38 -x15 -x341 -x194 x308 -x301 -x124 -x110 x90
0.29/0.39	v -x312 x92 -x42 x356 -x316 -x295 -x214 -x61 -x315 -x20 x362 -x296 -x267 x219 x86 -x64 -x266 -x185 x224 -x184 x87 -x365 x336 -x262
0.29/0.39	v x191 -x177 -x16 -x340 x195 x353 x304 -x299 -x125 x91 x303 x358 x320 -x60 -x213 x363 x329 -x215 -x66 x220 x366 -x364 x186 x338
0.29/0.39	v -x263 x187 -x69 x342 x323 -x300 x352 x324 x354 -x326 x319 -x62 x359 x328 x317 -x67 x367 -x333 x216 -x332 x228 -x70 -x68 x339
0.29/0.39	v x321 -x325 x355 x63 x330 -x318 -x225 x371 -x227 x71 x370 -x334 -x335 -x322 x327 -x226 x331 x368 -x369 x372 x1

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

/tmp/evaluation/365252-1177047701/instance-365252-1177047701.opb is already a linear file

Watcher Data (download as text)

runsolver version 3.2.2 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node44/watcher-365252-1177047701 -o ROOT/results/node44/solver-365252-1177047701 -C 1800 -W 3600 -M 1800 --output-limit 1,15 glpPBv3 /tmp/evaluation/365252-1177047701/instance-365252-1177047701.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.92 0.98 0.99 3/77 11380
/proc/meminfo: memFree=1747392/2055920 swapFree=4156080/4192956
[pid=11380] ppid=11378 vsize=2644 CPUtime=0
/proc/11380/stat : 11380 (glpPBv3) R 11378 11380 9669 0 -1 0 258 0 0 0 0 0 0 0 18 0 1 0 152681863 2707456 228 18446744073709551615 134512640 134678228 4294956704 18446744073709551615 11747031 0 0 4096 0 0 0 0 17 1 0 0
/proc/11380/statm: 661 228 192 40 0 76 0

[startup+0.0800431 s]
/proc/loadavg: 0.92 0.98 0.99 3/77 11380
/proc/meminfo: memFree=1747392/2055920 swapFree=4156080/4192956
[pid=11380] ppid=11378 vsize=3204 CPUtime=0.07
/proc/11380/stat : 11380 (glpPBv3) R 11378 11380 9669 0 -1 0 452 0 0 0 7 0 0 0 18 0 1 0 152681863 3280896 421 18446744073709551615 134512640 134678228 4294956704 18446744073709551615 134632412 0 0 4096 0 0 0 0 17 1 0 0
/proc/11380/statm: 801 421 227 40 0 216 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 3204

[startup+0.101046 s]
/proc/loadavg: 0.92 0.98 0.99 3/77 11380
/proc/meminfo: memFree=1747392/2055920 swapFree=4156080/4192956
[pid=11380] ppid=11378 vsize=3356 CPUtime=0.09
/proc/11380/stat : 11380 (glpPBv3) R 11378 11380 9669 0 -1 0 462 0 0 0 9 0 0 0 18 0 1 0 152681863 3436544 431 18446744073709551615 134512640 134678228 4294956704 18446744073709551615 134643697 0 0 4096 0 0 0 0 17 1 0 0
/proc/11380/statm: 839 431 227 40 0 254 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3356

[startup+0.301066 s]
/proc/loadavg: 0.92 0.98 0.99 3/77 11380
/proc/meminfo: memFree=1747392/2055920 swapFree=4156080/4192956
[pid=11380] ppid=11378 vsize=3356 CPUtime=0.29
/proc/11380/stat : 11380 (glpPBv3) R 11378 11380 9669 0 -1 0 489 0 0 0 29 0 0 0 19 0 1 0 152681863 3436544 458 18446744073709551615 134512640 134678228 4294956704 18446744073709551615 134569960 0 0 4096 0 0 0 0 17 1 0 0
/proc/11380/statm: 839 458 227 40 0 254 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3356

Solver just ended. Dumping a history of the last processes samples

Child status: 30
Real time (s): 0.394152
CPU time (s): 0.38994
CPU user time (s): 0.386941
CPU system time (s): 0.002999
CPU usage (%): 98.9314
Max. virtual memory (cumulated for all children) (KiB): 3356

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.386941
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 499
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 13
involuntary context switches= 0

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node44 on Fri Apr 20 05:41:42 UTC 2007

IDJOB= 365252
IDBENCH= 2222
IDSOLVER= 166
FILE ID= node44/365252-1177047701

PBS_JOBID= 4640123

Free space on /tmp= 66412 MiB

SOLVER NAME= glpPB 0.2
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/radar/normalized-10:10:4.5:0.5:100.opb
COMMAND LINE= glpPBv3 /tmp/evaluation/365252-1177047701/instance-365252-1177047701.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node44/convwatcher-365252-1177047701 -o ROOT/results/node44/conversion-365252-1177047701 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/365252-1177047701/instance-365252-1177047701.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node44/watcher-365252-1177047701 -o ROOT/results/node44/solver-365252-1177047701 -C 1800 -W 3600 -M 1800 --output-limit 1,15  glpPBv3 /tmp/evaluation/365252-1177047701/instance-365252-1177047701.opb

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  4dfe0aab63c58302cf08520fc713ceae

RANDOM SEED= 902796722

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node44.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.234
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.234
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:       1747736 kB
Buffers:         36124 kB
Cached:         183916 kB
SwapCached:      13744 kB
Active:          97376 kB
Inactive:       146836 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1747736 kB
SwapTotal:     4192956 kB
SwapFree:      4156080 kB
Dirty:            2316 kB
Writeback:           0 kB
Mapped:          32340 kB
Slab:            49424 kB
Committed_AS:   558988 kB
PageTables:       1736 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66412 MiB

End job on node44 on Fri Apr 20 05:41:42 UTC 2007