Trace number 50261

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/05OPT6 0.102983 0.181336

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/
manquiho/logic_synthesis/normalized-dk512x.r.opb
MD5SUM581a8e804be9894a02ef91830c95d4b0
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark6
Best CPU time to get the best result obtained on this benchmark0.032994
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 6
Optimality of the best value was proved YES
Number of variables59
Total number of constraints91
Number of constraints which are clauses91
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 constraint53
Number of terms in the objective function 59
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 59
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 59
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c Time Limit set via PBTIMEOUT to 1800
0.08	c INFO: OSL Context initialized.
0.09	c Initial problem consists of 59 variables and 91 constraints.
0.09	c Switching on LPR.
0.09	c No problem reductions applied in OPT. instance.
0.09	c	preprocess terminated. Elapsed time: 0.019
0.09	c After prepocess the problem consists of 57 variables and 40 constraints.
0.10	c Initial Lower Bound: 5
0.11	o 6
0.11	c NEW SOLUTION FOUND: 6 @ 0.035
0.17	s OPTIMUM FOUND
0.17	c Cost: 6
0.17	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
0.17	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
0.17	v -x56 -x57 -x58 -x59
0.17	c Exit Code: 30
0.17	c Total time: 0.1 s

Verifier Data (download as text)

OK	6

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.92 0.97 0.91 2/64 4749
/proc/meminfo: memFree=1413512/2055920 swapFree=4182220/4192956
[pid=4749] ppid=4747 vsize=4932 CPUtime=0
/proc/4749/stat : 4749 (bsolo) D 4747 4749 4703 0 -1 0 366 0 0 0 0 0 0 0 19 0 1 0 253687392 5050368 330 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 2147483391 4096 16384 18446744072099781622 0 0 17 1 0 0
/proc/4749/statm: 1233 330 226 55 0 125 0

Child status: 30
Real time (s): 0.181336
CPU time (s): 0.102983
CPU user time (s): 0.092985
CPU system time (s): 0.009998
CPU usage (%): 56.7912
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node70 on Fri Jun  9 19:09:38 UTC 2006


FILE ID= 50261-1149880178

PBS_JOBID= 384642

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  581a8e804be9894a02ef91830c95d4b0

RANDOM SEED= 767803373


/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.265
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.265
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:       1413784 kB
Buffers:         42620 kB
Cached:         521120 kB
SwapCached:       2428 kB
Active:         114520 kB
Inactive:       457928 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1413784 kB
SwapTotal:     4192956 kB
SwapFree:      4182220 kB
Dirty:             160 kB
Writeback:           0 kB
Mapped:          15464 kB
Slab:            55756 kB
Committed_AS:   522060 kB
PageTables:       1416 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node70 on Fri Jun  9 19:09:38 UTC 2006