Trace number 41712

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
PBS 4.1LOPT36 0.028995 0.031748

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB05/manquinho/routing/normalized-s3-3-3-1pb.opb
MD5SUM080a02d7e8292b0391648332c67d084b
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark36
Best CPU time to get the best result obtained on this benchmark0.014996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 36
Optimality of the best value was proved YES
Number of variables216
Total number of constraints584
Number of constraints which are clauses572
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 constraint18
Number of terms in the objective function 216
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 216
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 216
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 PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00	c Solving ROOT/tmp/node84/41712-1149404313/instance-41712-1149404313.opb ......
0.02	c done parsing opb.
0.02	o 36
0.03	o 36
0.03	s OPTIMUM FOUND
0.03	c Total Run Time					0.020997
0.03	v x1 -x10 -x100 x101 x102 -x103 -x104 -x105 x106 -x107 -x108 -x109 x11 x110 x111 -x112 -x113 -x114 -x115 x116 -x117 -x118 -x119
0.03	v -x12 -x120 -x121 -x122 x123 x124 -x125 -x126 -x127 -x128 -x129 -x13 -x130 -x131 -x132 -x133 -x134 x135 -x136 -x137 -x138 -x139
0.03	v -x14 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 x148 -x149 -x15 x150 -x151 -x152 -x153 -x154 -x155 x156 -x157 -x158 -x159
0.03	v -x16 -x160 x161 x162 -x163 -x164 -x165 -x166 -x167 -x168 -x169 -x17 -x170 -x171 -x172 -x173 -x174 x175 -x176 -x177 -x178 -x179
0.03	v -x18 -x180 -x181 -x182 -x183 -x184 -x185 -x186 x187 -x188 -x189 -x19 x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198
0.03	v -x199 -x2 -x20 -x200 -x201 x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 x21 -x210 x211 -x212 -x213 -x214 -x215 -x216 -x22
0.03	v -x23 -x24 -x25 -x26 -x27 -x28 x29 -x3 -x30 -x31 -x32 -x33 -x34 x35 -x36 x37 x38 -x39 -x4 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47
0.03	v -x48 -x49 -x5 x50 -x51 -x52 -x53 -x54 -x55 -x56 x57 -x58 -x59 -x6 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 x69 -x7 -x70 -x71
0.03	v x72 -x73 -x74 -x75 x76 -x77 -x78 -x79 x8 -x80 -x81 -x82 -x83 x84 x85 -x86 -x87 -x88 -x89 -x9 -x90 -x91 x92 -x93 -x94 x95 -x96 -x97
0.03	v -x98 -x99

Verifier Data (download as text)

OK	36

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node84/watcher-41712-1149404313 -o ROOT/results/node84/solver-41712-1149404313 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node84/41712-1149404313/instance-41712-1149404313.opb 37993340 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.93 0.96 0.94 3/67 2291
/proc/meminfo: memFree=1843928/2055892 swapFree=4085292/4096564
[pid=2291] ppid=2289 vsize=1400 CPUtime=0
/proc/2291/stat : 2291 (PBS4L) R 2289 2291 2245 0 -1 4194304 148 0 0 0 0 0 0 0 18 0 1 0 206070628 1433600 132 18446744073709551615 134512640 135466232 4294956672 18446744073709551615 135084712 0 0 4096 0 0 0 0 17 1 0 0
/proc/2291/statm: 350 132 100 232 0 115 0

Child status: 0
Real time (s): 0.031748
CPU time (s): 0.028995
CPU user time (s): 0.028995
CPU system time (s): 0
CPU usage (%): 91.3287
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node84 on Sun Jun  4 06:58:33 UTC 2006


FILE ID= 41712-1149404313

PBS_JOBID= 314277

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/routing/normalized-s3-3-3-1pb.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node84/41712-1149404313/instance-41712-1149404313.opb 37993340
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-41712-1149404313 -o ROOT/results/node84/solver-41712-1149404313 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user11/PBS4L ROOT/tmp/node84/41712-1149404313/instance-41712-1149404313.opb 37993340

MD5SUM SOLVER= ab46593c31a6a47b9d9920387a00d332
MD5SUM BENCH=  080a02d7e8292b0391648332c67d084b

RANDOM SEED= 37993340


/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.231
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	: 6006.15
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.231
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1844200 kB
Buffers:         15872 kB
Cached:         131676 kB
SwapCached:       2324 kB
Active:          38080 kB
Inactive:       117980 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1844200 kB
SwapTotal:     4096564 kB
SwapFree:      4085292 kB
Dirty:             288 kB
Writeback:           0 kB
Mapped:          16424 kB
Slab:            42348 kB
Committed_AS:   445088 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Sun Jun  4 06:58:33 UTC 2006