Trace number 36849

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
Pueblo 1.4OPT15 24.3983 24.4095

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/logic-synthesis/normalized-clip.b.opb
MD5SUM3b68d80e8ba1b8a702f9c691105ea9d4
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark15
Best CPU time to get the best result obtained on this benchmark1.10183
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 15
Optimality of the best value was proved YES
Number of variables349
Total number of constraints707
Number of constraints which are clauses707
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint111
Number of terms in the objective function 349
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 349
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 349
Number of bits of the biggest sum of numbers9
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 Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.05	c starting to Solve
0.05	c #variables read: 349 - #constraints read: 706
0.05	o 21
0.05	o 20
0.06	o 19
0.06	o 18
0.07	o 17
0.09	o 16
6.45	o 15
24.40	c optimum objective found = 15
24.40	c total time              : 24.39 s
24.40	s OPTIMUM FOUND
24.40	v -x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 -x17 -x18 -x19 -x20 -x21 -x22 -x23 -x24 x25 -x26 -x27 -x28
24.40	v -x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 x53 -x54
24.40	v -x55 -x56 x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80
24.40	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 x89 -x90 -x91 -x92 -x93 x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105
24.40	v -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125 -x126
24.40	v -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147
24.40	v -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168
24.40	v -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188 -x189
24.40	v -x190 -x191 -x192 x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209 -x210
24.40	v -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x230 -x231
24.40	v -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239 -x240 -x241 -x242 -x243 -x244 -x245 -x246 -x247 -x248 -x249 x250 -x251 -x252
24.40	v -x253 -x254 -x255 -x256 -x257 -x258 -x259 -x260 -x261 -x262 -x263 -x264 -x265 -x266 -x267 -x268 x269 -x270 -x271 -x272 -x273
24.40	v -x274 -x275 -x276 -x277 -x278 -x279 -x280 -x281 -x282 -x283 -x284 -x285 -x286 -x287 -x288 -x289 -x290 -x291 -x292 -x293 -x294
24.40	v -x295 -x296 -x297 -x298 -x299 -x300 -x301 x302 -x303 -x304 -x305 x306 -x307 -x308 -x309 -x310 -x311 -x312 x313 -x314 -x315
24.40	v -x316 -x317 -x318 -x319 -x320 -x321 -x322 -x323 -x324 -x325 -x326 -x327 -x328 -x329 -x330 -x331 -x332 -x333 -x334 -x335 -x336
24.40	v -x337 -x338 -x339 -x340 -x341 x342 -x343 -x344 -x345 -x346 x347 -x348 -x349

Verifier Data (download as text)

OK	15

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/node50/watcher-36849-1149407486 -o ROOT/results/node50/solver-36849-1149407486 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node50/36849-1149407486/instance-36849-1149407486.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 1.09 1.05 1.01 2/64 22026
/proc/meminfo: memFree=1558032/2055920 swapFree=4181340/4192956
[pid=22026] ppid=22024 vsize=2328 CPUtime=0
/proc/22026/stat : 22026 (Pueblo) R 22024 22026 21980 0 -1 4194304 146 0 0 0 0 0 0 0 18 0 1 0 206415794 2383872 127 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 7881923 0 0 4096 0 0 0 0 17 1 0 0
/proc/22026/statm: 582 128 109 16 0 11 0

[startup+10.0024 s]
/proc/loadavg: 1.16 1.06 1.01 2/64 22026
/proc/meminfo: memFree=1556072/2055920 swapFree=4181340/4192956
[pid=22026] ppid=22024 vsize=4316 CPUtime=9.99
/proc/22026/stat : 22026 (Pueblo) R 22024 22026 21980 0 -1 4194304 742 0 0 0 997 2 0 0 25 0 1 0 206415794 4419584 704 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134528630 0 0 4096 0 0 0 0 17 1 0 0
/proc/22026/statm: 1079 704 205 16 0 520 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 4316

[startup+20.0083 s]
/proc/loadavg: 1.13 1.06 1.01 2/64 22026
/proc/meminfo: memFree=1555944/2055920 swapFree=4181340/4192956
[pid=22026] ppid=22024 vsize=4676 CPUtime=19.99
/proc/22026/stat : 22026 (Pueblo) R 22024 22026 21980 0 -1 4194304 816 0 0 0 1993 6 0 0 25 0 1 0 206415794 4788224 778 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/22026/statm: 1169 778 205 16 0 610 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 4676

Child status: 30
Real time (s): 24.4095
CPU time (s): 24.3983
CPU user time (s): 24.3243
CPU system time (s): 0.073988
CPU usage (%): 99.9542
Max. virtual memory (cumulated for all children) (Kb): 4676

Launcher Data (download as text)

Begin job on node50 on Sun Jun  4 07:51:26 UTC 2006


FILE ID= 36849-1149407486

PBS_JOBID= 314495

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/logic-synthesis/normalized-clip.b.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node50/36849-1149407486/instance-36849-1149407486.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node50/watcher-36849-1149407486 -o ROOT/results/node50/solver-36849-1149407486 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node50/36849-1149407486/instance-36849-1149407486.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  3b68d80e8ba1b8a702f9c691105ea9d4

RANDOM SEED= 621806726


/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:       1558304 kB
Buffers:         25092 kB
Cached:         400696 kB
SwapCached:       3224 kB
Active:          35916 kB
Inactive:       398620 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1558304 kB
SwapTotal:     4192956 kB
SwapFree:      4181340 kB
Dirty:             192 kB
Writeback:           0 kB
Mapped:          14956 kB
Slab:            49064 kB
Committed_AS:   401356 kB
PageTables:       1480 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node50 on Sun Jun  4 07:51:51 UTC 2006