Trace number 365336

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.011997 0.013825

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.011997
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/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.00/0.01	c starting to Solve
0.00/0.01	c total time = 0
0.00/0.01	o 304
0.00/0.01	c quality of integer solution is H
0.00/0.01	s OPTIMUM FOUND
0.00/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.00/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.00/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.00/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.00/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.00/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.00/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.00/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.00/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.00/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.00/0.01	v x196 -x197 x201 x205 -x207 -x209 -x210 -x211 -x212 x219 x221 x223 x251 x252

Verifier Data (download as text)

OK	304

Conversion Script Data (download as text)

/tmp/evaluation/365336-1177049523/instance-365336-1177049523.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/node24/watcher-365336-1177049523 -o ROOT/results/node24/solver-365336-1177049523 -C 1800 -W 3600 -M 1800 --output-limit 1,15 glpPBv3 /tmp/evaluation/365336-1177049523/instance-365336-1177049523.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.97 1.16 1.16 3/77 17761
/proc/meminfo: memFree=1528768/2055920 swapFree=4138812/4192956
[pid=17761] ppid=17759 vsize=2648 CPUtime=0
/proc/17761/stat : 17761 (glpPBv3) R 17759 17761 25994 0 -1 0 266 0 0 0 0 0 0 0 18 0 1 0 152870386 2711552 236 18446744073709551615 134512640 134678228 4294956704 18446744073709551615 134530899 0 0 4096 0 0 0 0 17 1 0 0
/proc/17761/statm: 662 236 199 40 0 77 0

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

Child status: 30
Real time (s): 0.013825
CPU time (s): 0.011997
CPU user time (s): 0.008998
CPU system time (s): 0.002999
CPU usage (%): 86.7777
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.008998
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= 377
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= 12
involuntary context switches= 0

runsolver used 0.005999 second user time and 0.001999 second system time

The end

Launcher Data (download as text)

Begin job on node24 on Fri Apr 20 06:12:03 UTC 2007

IDJOB= 365336
IDBENCH= 2232
IDSOLVER= 166
FILE ID= node24/365336-1177049523

PBS_JOBID= 4640163

Free space on /tmp= 66233 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/course-ass/normalized-ss97-6.opb
COMMAND LINE= glpPBv3 /tmp/evaluation/365336-1177049523/instance-365336-1177049523.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node24/convwatcher-365336-1177049523 -o ROOT/results/node24/conversion-365336-1177049523 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/365336-1177049523/instance-365336-1177049523.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  dcfce19ac0444148b26b7675e35c76bc

RANDOM SEED= 888262946

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node24.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.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:       1529176 kB
Buffers:         65948 kB
Cached:         362692 kB
SwapCached:      22200 kB
Active:         172752 kB
Inactive:       291860 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1529176 kB
SwapTotal:     4192956 kB
SwapFree:      4138812 kB
Dirty:            2484 kB
Writeback:           0 kB
Mapped:          41356 kB
Slab:            47608 kB
Committed_AS:  3681904 kB
PageTables:       1816 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= 66233 MiB

End job on node24 on Fri Apr 20 06:12:04 UTC 2007