Trace number 2696536

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-29OPT304 0.030994 0.031006

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.030994
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 

0.00/0.00	c pb_cplex 1.0 - 20100701
0.00/0.00	c Parsing opb file format. File HOME/instance-2696536-1278018940.opb.
0.00/0.00	c Instance file HOME/instance-2696536-1278018940.opb
0.00/0.00	c File size is 8127 bytes.
0.00/0.02	c Highest Coefficient sum: 62
0.00/0.02	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.02	c ============================[ Problem Statistics ]=============================
0.00/0.02	c |                                                                             |
0.00/0.02	c |  Parsing time:          0.02         s                                      |
0.00/0.02	c |  Number Variables:      257                                                 |
0.00/0.02	c |  Number Constraints:    97                                                  |
0.00/0.02	c ===============================================================================
0.00/0.03	c Remaining time 1799.98 sec.
0.00/0.03	s OPTIMUM FOUND
0.00/0.03	c Solution value = 304.00
0.00/0.03	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 x62 x20 -x108 -x109 x153 -x22 -x110 x154 -x111 x155 x112 -x192 x232 -x27 x71 x237 x118 -x198 x238 -x199 x239 x119 -x200 x240 x164 x121 -x202 x242 -x203 x243 x122 -x204 x244 -x124 x168 x206 -x246 x125 x247 -x38 -x126 x170 -x208 x248 x127 x249 -x40 x172 x250 -x213 x253 x130 x214 -x254 x131 x215 -x255 x132 -x216 x256 -x133 x257 -x2 -x46 -x90 -x91 -x179 -x48 -x220 -x222 -x224 -x53 -x141 -x12 -x56 -x144 -x228 -x57 -x145 -x229 -x58 -x146 -x103 -x147 -x16 -x148 -x18 -x150 -x19 x63 -x107 -x151 -x152 -x66 -x24 -x68 -x156 -x25 x69 -x113 -x157 -x191 x231 -x159 -x233 -x234 -x235 -x236 -x30 -x74 -x162 -x31 -x75 -x163 -x76 -x120 -x241 -x33 -x77 -x165 -x34 -x166 -x35 -x79 -x245 -x80 -x81 -x169 -x82 -x39 -x83 -x171 -x84 -x128 -x42 -x86 -x174 -x43 -x87 -x175 -x44 -x88 -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 -x60 -x64 -x65 -x67 x70 x72 -x73 -x78 x85 -x89 -x92 -x93 -x94 -x95 -x96 -x98 -x101 -x102 -x106 -x114 -x115 -x116 -x117 -x123 -x129 -x135 -x136 -x137 -x138 -x139 -x140 -x142 -x158 -x160 -x161 x167 -x173 x181 x182 x183 x184 x188 x189 -x190 x193 x194 x195 x196 -x197 x201 x205 -x207 -x209 -x210 x211 x212 x219 -x221 -x223 -x251 -x252
0.00/0.03	c Total CPU time              : 0.021996 s

Verifier Data 

OK	304

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2696536-1278018940/watcher-2696536-1278018940 -o /tmp/evaluation-result-2696536-1278018940/solver-2696536-1278018940 -C 1800 -W 2000 -M 1800 run HOME/instance-2696536-1278018940.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: 1.93 1.93 1.70 3/106 2665
/proc/meminfo: memFree=1629824/2059040 swapFree=4192956/4192956
[pid=2665] ppid=2663 vsize=8700 CPUtime=0
/proc/2665/stat : 2665 (run) S 2663 2665 2453 0 -1 4202496 364 0 0 0 0 0 0 0 25 0 1 0 208898 8908800 249 1992294400 4194304 4922060 140736312637760 18446744073709551615 236997680261 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/2665/statm: 2175 249 208 178 0 68 0

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

Child status: 0
Real time (s): 0.031006
CPU time (s): 0.030994
CPU user time (s): 0.022996
CPU system time (s): 0.007998
CPU usage (%): 99.9613
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node027 at 2010-07-01 23:15:40
IDJOB=2696536
IDBENCH=2232
IDSOLVER=1209
FILE ID=node027/2696536-1278018940
PBS_JOBID= 11198754
Free space on /tmp= 61856 MiB

SOLVER NAME= pb_cplex 2010-06-29
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/course-ass/normalized-ss97-6.opb
COMMAND LINE= run BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2696536-1278018940/watcher-2696536-1278018940 -o /tmp/evaluation-result-2696536-1278018940/solver-2696536-1278018940 -C 1800 -W 2000 -M 1800  run HOME/instance-2696536-1278018940.opb

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

MD5SUM BENCH= dcfce19ac0444148b26b7675e35c76bc
RANDOM SEED=217928462

node027.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		: 2800.179
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	: 5600.35
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		: 2800.179
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.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1630228 kB
Buffers:         56464 kB
Cached:         264252 kB
SwapCached:          0 kB
Active:         159664 kB
Inactive:       220276 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1630228 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:           16632 kB
Writeback:           0 kB
AnonPages:       59216 kB
Mapped:          14396 kB
Slab:            26848 kB
PageTables:       4172 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   179616 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264952 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 61840 MiB
End job on node027 at 2010-07-01 23:15:40