Trace number 50265

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
bsolo 2006/05OPT12 13.169 13.1923

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
logic_synthesis/normalized-m100_100_10_10.r.opb
MD5SUM863d0ff562dc066d0163e86da5775aea
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark12
Best CPU time to get the best result obtained on this benchmark13.169
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 12
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 constraint10
Maximum length of a constraint10
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 Time Limit set via PBTIMEOUT to 1800
0.02	c INFO: OSL Context initialized.
0.02	c Initial problem consists of 100 variables and 100 constraints.
0.02	c Switching on LPR.
0.02	c No problem reductions applied in OPT. instance.
0.02	c	preprocess terminated. Elapsed time: 0.009
0.02	c After prepocess the problem consists of 100 variables and 100 constraints.
0.04	c Initial Lower Bound: 10
0.09	o 13
0.09	c NEW SOLUTION FOUND: 13 @ 0.074
0.79	c Restart #1 #Var: 100 LB: 10 @ 0.774
2.36	c Restart #2 #Var: 100 LB: 10 @ 2.344
5.24	c Restart #3 #Var: 100 LB: 10 @ 5.228
9.86	c Restart #4 #Var: 100 LB: 10 @ 9.848
10.25	o 12
10.25	c NEW SOLUTION FOUND: 12 @ 10.235
13.19	s OPTIMUM FOUND
13.19	c Cost: 12
13.19	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.19	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 -x56
13.19	v -x57 -x58 -x59 -x60 -x61 -x62 -x63 x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 x76 -x77 -x78 -x79 -x80 -x81 -x82
13.19	v -x83 x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 x98 -x99 -x100
13.19	c Exit Code: 30
13.19	c Total time: 13.167 s

Verifier Data (download as text)

OK	12

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/node68/watcher-50265-1149881929 -o ROOT/results/node68/solver-50265-1149881929 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node68/50265-1149881929/instance-50265-1149881929.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 5167
/proc/meminfo: memFree=1628736/2055920 swapFree=4182328/4192956
[pid=5167] ppid=5165 vsize=2900 CPUtime=0
/proc/5167/stat : 5167 (bsolo) R 5165 5167 5121 0 -1 0 43 0 0 0 0 0 0 0 18 0 1 0 253862429 2969600 27 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10514731 0 0 4096 0 0 0 0 17 1 0 0
/proc/5167/statm: 725 27 19 55 0 38 0

[startup+10.0023 s]
/proc/loadavg: 0.93 0.95 0.90 2/64 5167
/proc/meminfo: memFree=1626648/2055920 swapFree=4182328/4192956
[pid=5167] ppid=5165 vsize=6876 CPUtime=9.97
/proc/5167/stat : 5167 (bsolo) R 5165 5167 5121 0 -1 0 9579 0 0 0 987 10 0 0 25 0 1 0 253862429 7041024 993 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10948045 0 0 4096 16384 0 0 0 17 1 0 0
/proc/5167/statm: 1719 993 428 55 0 611 0
Current children cumulated CPU time (s) 9.97
Current children cumulated vsize (Kb) 6876

Child status: 30
Real time (s): 13.1923
CPU time (s): 13.169
CPU user time (s): 13.022
CPU system time (s): 0.146977
CPU usage (%): 99.8236
Max. virtual memory (cumulated for all children) (Kb): 6876
The end

Launcher Data (download as text)

Begin job on node68 on Fri Jun  9 19:38:49 UTC 2006


FILE ID= 50265-1149881929

PBS_JOBID= 384694

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-m100_100_10_10.r.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node68/50265-1149881929/instance-50265-1149881929.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node68/watcher-50265-1149881929 -o ROOT/results/node68/solver-50265-1149881929 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node68/50265-1149881929/instance-50265-1149881929.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  863d0ff562dc066d0163e86da5775aea

RANDOM SEED= 480345065


/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.279
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.279
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:       1628944 kB
Buffers:         41860 kB
Cached:         309628 kB
SwapCached:       2384 kB
Active:         114852 kB
Inactive:       245388 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1628944 kB
SwapTotal:     4192956 kB
SwapFree:      4182328 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          15560 kB
Slab:            52820 kB
Committed_AS:   607404 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node68 on Fri Jun  9 19:39:02 UTC 2006