Trace number 50030

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.3OPT4 12.2021 12.2114

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
logic_synthesis/normalized-m100_100_50_50.r.opb
MD5SUM92218ddb5567427e70962e6332b1ed9e
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark4
Best CPU time to get the best result obtained on this benchmark1.46578
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 4
Optimality of the best value was proved YES
Number of variables100
Total number of constraints100
Number of constraints which are clauses100
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 constraint50
Maximum length of a constraint50
Number of terms in the objective function 100
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 100
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 100
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.02	c starting to Solve
0.02	c #variables read: 100 - #constraints read: 101
0.02	o 6
0.02	o 5
0.09	o 4
12.21	c optimum objective found = 4
12.21	c total time              : 12.19 s
12.21	s OPTIMUM FOUND
12.21	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
12.21	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
12.21	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
12.21	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 x93 -x94 -x95 -x96 -x97 -x98 x99 -x100

Verifier Data (download as text)

OK	4

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.92 0.96 2/64 4282
/proc/meminfo: memFree=1916448/2055920 swapFree=4192956/4192956
[pid=4282] ppid=4280 vsize=2328 CPUtime=0
/proc/4282/stat : 4282 (Pueblo13) R 4280 4282 4236 0 -1 4194304 141 0 0 0 0 0 0 0 18 0 1 0 1175212 2383872 124 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 6928043 0 0 4096 0 0 0 0 17 1 0 0
/proc/4282/statm: 582 127 108 16 0 11 0

[startup+10.0013 s]
/proc/loadavg: 0.81 0.92 0.96 2/64 4282
/proc/meminfo: memFree=1916040/2055920 swapFree=4192956/4192956
[pid=4282] ppid=4280 vsize=2836 CPUtime=9.98
/proc/4282/stat : 4282 (Pueblo13) R 4280 4282 4236 0 -1 4194304 335 0 0 0 979 19 0 0 25 0 1 0 1175212 2904064 306 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/4282/statm: 709 306 205 16 0 150 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 2836

Child status: 30
Real time (s): 12.2114
CPU time (s): 12.2021
CPU user time (s): 11.9762
CPU system time (s): 0.225965
CPU usage (%): 99.9238
Max. virtual memory (cumulated for all children) (Kb): 2836
The end

Launcher Data (download as text)

Begin job on node64 on Fri Jun  9 20:27:45 UTC 2006


FILE ID= 50030-1149884865

PBS_JOBID= 384809

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

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  92218ddb5567427e70962e6332b1ed9e

RANDOM SEED= 605670504


/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.263
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.263
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:       1916656 kB
Buffers:         17936 kB
Cached:          77944 kB
SwapCached:          0 kB
Active:          63084 kB
Inactive:        47180 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1916656 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             312 kB
Writeback:           0 kB
Mapped:          24788 kB
Slab:            15024 kB
Committed_AS:    60584 kB
PageTables:       1476 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node64 on Fri Jun  9 20:27:57 UTC 2006