Trace number 2696532

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
pb_cplex 2010-06-29OPT1 0.079987 0.081194

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/
benchmarks/radar/normalized-10:10:4.5:0.95:98.opb
MD5SUM7acfcd4d612717a490c27c9a55b3f455
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark1
Best CPU time to get the best result obtained on this benchmark0.079987
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 1
Optimality of the best value was proved YES
Number of variables411
Total number of constraints477
Number of constraints which are clauses387
Number of constraints which are cardinality constraints (but not clauses)90
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint16
Number of terms in the objective function 411
Biggest coefficient in the objective function 268
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 1129
Number of bits of the sum of numbers in the objective function 11
Biggest number in a constraint 268
Number of bits of the biggest number in a constraint 9
Biggest sum of numbers in a constraint 1129
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c pb_cplex 1.0 - 20100701
0.00/0.00	c Parsing opb file format. File HOME/instance-2696532-1278018938.opb.
0.00/0.00	c Instance file HOME/instance-2696532-1278018938.opb
0.00/0.00	c File size is 19110 bytes.
0.00/0.05	c Highest Coefficient sum: 19
0.00/0.05	c  IBM ILOG License Manager: "IBM ILOG Optimization Suite for Academic Initiative" is accessing CPLEX 12 with option(s): "e m b q ".
0.00/0.05	c ============================[ Problem Statistics ]=============================
0.00/0.05	c |                                                                             |
0.00/0.05	c |  Parsing time:          0.05         s                                      |
0.00/0.05	c |  Number Variables:      411                                                 |
0.00/0.05	c |  Number Constraints:    477                                                 |
0.00/0.05	c ===============================================================================
0.00/0.07	c Remaining time 1799.95 sec.
0.00/0.07	s OPTIMUM FOUND
0.00/0.07	c Solution value = 1.00
0.00/0.07	v x295 -x231 x206 x191 -x139 x294 x211 x192 -x143 -x359 -x302 x279 -x235 x210 x196 x296 -x233 x195 -x358 x297 x213 x193 -x119 x362 x298 -x234 x214 -x194 -x180 -x83 -x238 x217 -x179 -x164 -x118 x82 x363 x215 -x122 x84 x216 -x181 -x163 x85 x184 x168 -x123 x86 x305 -x275 -x230 x190 -x138 x306 x205 x189 -x142 x385 -x301 x278 -x236 x207 -x200 x212 -x360 -x313 -x299 -x239 x209 -x37 x364 -x317 -x237 x218 -x175 -x174 -x120 -x124 -x366 -x182 -x165 -x89 -x367 x183 x167 x90 -x381 x303 -x274 -x228 -x203 x140 -x354 -x232 x204 -x144 x384 -x353 x280 -x229 -x199 -x33 -x240 x208 -x114 -x361 -x312 -x300 -x226 -x197 x146 -x113 -x36 x365 -x316 x222 -x159 -x147 x369 x283 -x221 x158 -x121 -x88 x368 x176 -x125 -x87 -x342 x177 x166 -x126 -x71 x178 x169 -x127 x75 -x380 x304 -x276 -x201 x141 -x227 x145 -x397 x386 x281 -x248 -x223 x149 -x32 -x401 -x355 -x244 -x225 x148 -x356 -x314 x284 -x243 -x198 -x38 -x8 x357 -x318 x282 -x115 -x12 -x389 x373 -x338 -x219 -x116 -x101 x160 -x117 -x341 x320 -x220 x187 x161 -x131 -x70 -x41 -x321 x188 x162 x74 x382 x272 -x245 -x202 x137 -x28 -x308 -x277 -x247 -x224 x136 -x396 x387 -x307 x273 x153 -x34 -x400 x285 -x390 -x376 x315 -x241 -x97 -x39 -x7 -x388 x377 x319 -x11 -x372 -x337 x323 -x242 -x186 -x134 -x100 -x42 x322 x185 -x135 -x40 -x370 -x343 -x255 x172 -x130 -x72 -x259 x173 x76 x379 x265 -x246 -x156 x383 x271 x157 -x27 x398 -x375 x293 -x152 -x29 x402 x391 -x374 -x309 x289 -x35 -x333 x310 -x288 -x150 -x133 x96 -x31 -x9 x311 -x132 -x66 -x43 -x13 -x404 x339 -x327 x171 -x102 -x65 -x405 x170 -x371 -x344 -x254 -x128 x73 -x61 -x15 -x258 x77 -x16 -x290 x264 -x154 x378 -x292 -x3 x399 -x92 -x2 x403 x395 -x30 x407 x394 -x330 -x286 -x151 x98 -x51 -x10 x406 -x332 x331 -x47 -x14 -x334 -x326 -x287 -x103 -x57 -x46 -x18 x340 x67 -x17 x336 -x324 -x256 -x129 -x104 x68 -x60 x345 -x260 -x105 x69 -x291 x266 -x155 -x329 -x48 -x328 -x91 -x50 -x4 x411 x392 x268 -x93 -x5 -x250 x99 -x6 x393 -x249 x95 x56 -x44 -x22 x335 -x106 x352 -x325 x257 x80 -x62 -x45 x348 -x261 x81 -x49 x269 x267 -x410 x54 -x25 x94 -x26 -x408 x349 x112 -x79 x58 -x21 x351 x251 -x109 -x78 x252 -x107 x63 -x19 x346 x253 x270 -x24 -x23 x111 x350 x110 x53 -x409 x52 x59 x263 -x108 x55 -x20 x347 x262 x64 x1
0.00/0.07	c Total CPU time              : 0.068989 s

Verifier Data 

OK	1

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2696532-1278018938/watcher-2696532-1278018938 -o /tmp/evaluation-result-2696532-1278018938/solver-2696532-1278018938 -C 1800 -W 2000 -M 1800 run HOME/instance-2696532-1278018938.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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.53 2.42 2.05 3/106 21172
/proc/meminfo: memFree=1871520/2059040 swapFree=4135864/4192956
[pid=21172] ppid=21170 vsize=8700 CPUtime=0
/proc/21172/stat : 21172 (run) S 21170 21172 20758 0 -1 4202496 364 0 0 0 0 0 0 0 18 0 1 0 177495170 8908800 249 1992294400 4194304 4922060 140733206456688 18446744073709551615 255345663109 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/21172/statm: 2175 249 208 178 0 68 0

[startup+0.0279549 s]
/proc/loadavg: 2.53 2.42 2.05 3/106 21172
/proc/meminfo: memFree=1871520/2059040 swapFree=4135864/4192956
[pid=21172] ppid=21170 vsize=8700 CPUtime=0
/proc/21172/stat : 21172 (run) S 21170 21172 20758 0 -1 4202496 364 0 0 0 0 0 0 0 18 0 1 0 177495170 8908800 249 1992294400 4194304 4922060 140733206456688 18446744073709551615 255345663109 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/21172/statm: 2175 249 208 178 0 68 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8700

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

[startup+0.0279549 s]
/proc/loadavg: 2.53 2.42 2.05 3/106 21172
/proc/meminfo: memFree=1871520/2059040 swapFree=4135864/4192956
[pid=21172] ppid=21170 vsize=8700 CPUtime=0
/proc/21172/stat : 21172 (run) S 21170 21172 20758 0 -1 4202496 364 0 0 0 0 0 0 0 18 0 1 0 177495170 8908800 249 1992294400 4194304 4922060 140733206456688 18446744073709551615 255345663109 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/21172/statm: 2175 249 208 178 0 68 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8700

Child status: 0
Real time (s): 0.081194
CPU time (s): 0.079987
CPU user time (s): 0.069989
CPU system time (s): 0.009998
CPU usage (%): 98.5135
Max. virtual memory (cumulated for all children) (KiB): 8700

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.069989
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1911
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= 9
involuntary context switches= 3

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node014 at 2010-07-01 23:15:38
IDJOB=2696532
IDBENCH=2226
IDSOLVER=1209
FILE ID=node014/2696532-1278018938
PBS_JOBID= 11198741
Free space on /tmp= 62444 MiB

SOLVER NAME= pb_cplex 2010-06-29
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/radar/normalized-10:10:4.5:0.95:98.opb
COMMAND LINE= run BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2696532-1278018938/watcher-2696532-1278018938 -o /tmp/evaluation-result-2696532-1278018938/solver-2696532-1278018938 -C 1800 -W 2000 -M 1800  run HOME/instance-2696532-1278018938.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 7acfcd4d612717a490c27c9a55b3f455
RANDOM SEED=1344642243

node014.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.258
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.51
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.258
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1872048 kB
Buffers:          5356 kB
Cached:          95352 kB
SwapCached:      10880 kB
Active:          70560 kB
Inactive:        44668 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1872048 kB
SwapTotal:     4192956 kB
SwapFree:      4135864 kB
Dirty:           16632 kB
Writeback:           0 kB
AnonPages:       12956 kB
Mapped:           8548 kB
Slab:            49772 kB
PageTables:       4172 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182972 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62428 MiB
End job on node014 at 2010-07-01 23:15:38