Trace number 45689

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
PB-smodels 1.31OPT34 0.941856 0.925718

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB05/manquinho/routing/normalized-s3-3-3-5pb.opb
MD5SUM05e70299ef2fa3c0cab13f366c1644bf
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark34
Best CPU time to get the best result obtained on this benchmark0.028994
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 34
Optimality of the best value was proved YES
Number of variables240
Total number of constraints646
Number of constraints which are clauses634
Number of constraints which are cardinality constraints (but not clauses)12
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint20
Number of terms in the objective function 240
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 240
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 3
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 240
Number of bits of the biggest sum of numbers8
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00	c Running pbsmodels-v1.31
0.34	o 36
0.82	o 34
0.92	s OPTIMUM FOUND
0.92	v x6 x11 x22 x30 x45 x48 x54 x57 x60 x65 x76 x86 x93 x96 x97 x104 x111 x123 x127 x139 x142 x147 x152 x157 x160 x164 x173 x175 x178 x185
0.92	v x193 x208 x218 x230 -x1 -x2 -x3 -x4 -x5 -x7 -x8 -x9 -x10 -x12 -x13 -x14 -x15 -x16 -x17 -x18 -x19 -x20 -x21 -x23 -x24 -x25 -x26 -x27
0.92	v -x28 -x29 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x46 -x47 -x49 -x50 -x51 -x52 -x53 -x55 -x56 -x58
0.92	v -x59 -x61 -x62 -x63 -x64 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x87 -x88
0.92	v -x89 -x90 -x91 -x92 -x94 -x95 -x98 -x99 -x100 -x101 -x102 -x103 -x105 -x106 -x107 -x108 -x109 -x110 -x112 -x113 -x114 -x115
0.92	v -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x124 -x125 -x126 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138
0.92	v -x140 -x141 -x143 -x144 -x145 -x146 -x148 -x149 -x150 -x151 -x153 -x154 -x155 -x156 -x158 -x159 -x161 -x162 -x163 -x165 -x166
0.92	v -x167 -x168 -x169 -x170 -x171 -x172 -x174 -x176 -x177 -x179 -x180 -x181 -x182 -x183 -x184 -x186 -x187 -x188 -x189 -x190 -x191
0.92	v -x192 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x209 -x210 -x211 -x212 -x213 -x214
0.92	v -x215 -x216 -x217 -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x231 -x232 -x233 -x234 -x235 -x236 -x237
0.92	v -x238 -x239 -x240

Verifier Data (download as text)

OK	34

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.1 (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/node33/watcher-45689-1149652113 -o ROOT/results/node33/solver-45689-1149652113 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node33/45689-1149652113/instance-45689-1149652113.opb 85091137 ROOT/tmp/node33/45689-1149652113 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.77 0.92 0.95 2/64 17042
/proc/meminfo: memFree=1762664/2055920 swapFree=4181328/4192956
[pid=17042] ppid=17040 vsize=5212 CPUtime=0
/proc/17042/stat : 17042 (runpbsmodels) R 17040 17042 16996 0 -1 4194304 82 0 0 0 0 0 0 0 19 0 1 0 230875113 5337088 55 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 210823745264 0 0 4096 0 0 0 0 17 1 0 0
/proc/17042/statm: 1303 67 50 169 0 14 0

Child status: 0
Real time (s): 0.925718
CPU time (s): 0.941856
CPU user time (s): 0.91986
CPU system time (s): 0.021996
CPU usage (%): 101.743
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node33 on Wed Jun  7 03:48:33 UTC 2006


FILE ID= 45689-1149652113

PBS_JOBID= 324188

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/routing/normalized-s3-3-3-5pb.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node33/45689-1149652113/instance-45689-1149652113.opb 85091137  ROOT/tmp/node33/45689-1149652113
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node33/watcher-45689-1149652113 -o ROOT/results/node33/solver-45689-1149652113 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node33/45689-1149652113/instance-45689-1149652113.opb 85091137  ROOT/tmp/node33/45689-1149652113

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  05e70299ef2fa3c0cab13f366c1644bf

RANDOM SEED= 85091137


/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.213
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.213
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:       1762872 kB
Buffers:         31368 kB
Cached:         198164 kB
SwapCached:       3368 kB
Active:          85640 kB
Inactive:       152624 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1762872 kB
SwapTotal:     4192956 kB
SwapFree:      4181328 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          14680 kB
Slab:            40788 kB
Committed_AS:   435984 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node33 on Wed Jun  7 03:48:34 UTC 2006