Trace number 50013

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.3OPT7 13.143 13.1529

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/
manquiho/logic_synthesis/normalized-maincont.r.opb
MD5SUM810dcf2b3e8c0450d72550588875745c
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark7
Best CPU time to get the best result obtained on this benchmark0.023995
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 7
Optimality of the best value was proved YES
Number of variables67
Total number of constraints105
Number of constraints which are clauses105
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 constraint3
Maximum length of a constraint48
Number of terms in the objective function 67
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 67
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 67
Number of bits of the biggest sum of numbers7
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.01	c starting to Solve
0.01	c #variables read: 67 - #constraints read: 106
0.01	o 11
0.01	o 10
0.01	o 9
0.01	o 8
0.04	o 7
13.15	c optimum objective found = 7
13.15	c total time              : 13.14 s
13.15	s OPTIMUM FOUND
13.15	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 x29
13.15	v -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 -x55
13.15	v -x56 -x57 x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67

Verifier Data (download as text)

OK	7

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/node85/watcher-50013-1149880021 -o ROOT/results/node85/solver-50013-1149880021 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node85/50013-1149880021/instance-50013-1149880021.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/68 12842
/proc/meminfo: memFree=1281840/2055892 swapFree=4085340/4096564
[pid=12842] ppid=12840 vsize=1140 CPUtime=0
/proc/12842/stat : 12842 (Pueblo13) R 12840 12842 12796 0 -1 4194304 58 0 0 0 0 0 0 0 18 0 1 0 253641312 1167360 43 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 11723232 0 0 4096 0 0 0 0 17 1 0 0
/proc/12842/statm: 583 47 36 16 0 10 0

[startup+10.0022 s]
/proc/loadavg: 0.93 0.95 0.90 2/68 12842
/proc/meminfo: memFree=1281736/2055892 swapFree=4085340/4096564
[pid=12842] ppid=12840 vsize=2708 CPUtime=9.99
/proc/12842/stat : 12842 (Pueblo13) R 12840 12842 12796 0 -1 4194304 303 0 0 0 929 70 0 0 25 0 1 0 253641312 2772992 275 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/12842/statm: 677 275 205 16 0 117 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 2708

Child status: 30
Real time (s): 13.1529
CPU time (s): 13.143
CPU user time (s): 12.2321
CPU system time (s): 0.910861
CPU usage (%): 99.9246
Max. virtual memory (cumulated for all children) (Kb): 2708
The end

Launcher Data (download as text)

Begin job on node85 on Fri Jun  9 19:07:01 UTC 2006


FILE ID= 50013-1149880021

PBS_JOBID= 384588

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-maincont.r.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node85/50013-1149880021/instance-50013-1149880021.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node85/watcher-50013-1149880021 -o ROOT/results/node85/solver-50013-1149880021 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node85/50013-1149880021/instance-50013-1149880021.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  810dcf2b3e8c0450d72550588875745c

RANDOM SEED= 986970452


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1282240 kB
Buffers:         44528 kB
Cached:         652756 kB
SwapCached:       2368 kB
Active:         119076 kB
Inactive:       586800 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1282240 kB
SwapTotal:     4096564 kB
SwapFree:      4085340 kB
Dirty:             268 kB
Writeback:           0 kB
Mapped:          16776 kB
Slab:            54332 kB
Committed_AS:   590900 kB
PageTables:       1292 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node85 on Fri Jun  9 19:07:14 UTC 2006