Trace number 50585

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
SAT4JPSEUDO 2006.2 HeuristicsOPT2 0.817875 0.587054

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
logic_synthesis/normalized-m50_100_70_70.r.opb
MD5SUMc2530fca17c8f1e59eb4e770d7ebf727
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.018997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables100
Total number of constraints50
Number of constraints which are clauses50
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 constraint70
Maximum length of a constraint70
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.15	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.15	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.15	c no version file found!!!
0.15	c sun.arch.data.model	32
0.15	c java.version	1.5.0_06
0.15	c os.name	Linux
0.15	c os.version	2.6.9-34.ELsmp
0.15	c os.arch	i386
0.15	c Free memory 1548419056
0.15	c Max memory 1551040512
0.15	c Total memory 1551040512
0.15	c Number of processors 2
0.21	c Cutting planes based inference
0.21	c --- Begin Solver configuration ---
0.21	c org.sat4j.minisat.uip.FirstUIP@1df073d
0.21	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1546e25
0.21	c org.sat4j.minisat.learning.MiniSATLearning@b66cc
0.21	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.21	c VSIDS like heuristics from MiniSAT using a heap
0.21	c No reason simplification
0.21	c --- End Solver configuration ---
0.21	c solving ROOT/tmp/node80/50585-1149872833/instance-50585-1149872833.opb
0.21	c reading problem ... 
0.40	c ... done. Time 0.196 ms.
0.40	c #vars     100
0.40	c #constraints  50
0.41	c SATISFIABLE
0.41	c OPTIMIZING...
0.41	c Got one! Ellapsed CPU time (in seconds):0.206
0.42	o 4
0.45	c Got one! Ellapsed CPU time (in seconds):0.242
0.45	o 3
0.54	c Got one! Ellapsed CPU time (in seconds):0.33
0.54	o 2
0.56	c starts		: 4
0.56	c conflicts		: 26
0.56	c decisions		: 449
0.56	c propagations		: 660
0.56	c inspects		: 1749
0.56	c learnt literals	: 0
0.56	c learnt binary clauses	: 0
0.56	c learnt ternary clauses	: 0
0.56	c learnt clauses	: 25
0.56	c root simplifications	: 0
0.56	c removed literals (reason simplification)	: 0
0.56	c reason swapping (by a shorter reason)	: 0
0.56	c Calls to reduceDB	: 0
0.56	c speed (decisions/second)	: 28062.5
0.56	c non guided choices	0
0.56	s OPTIMUM FOUND
0.56	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
0.56	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
0.56	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
0.56	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100
0.56	c objective function=2
0.56	c Total wall clock time (ms): 0.35

Verifier Data (download as text)

OK	2

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/node80/watcher-50585-1149872833 -o ROOT/results/node80/solver-50585-1149872833 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node80/50585-1149872833/instance-50585-1149872833.opb 207743099 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.00 0.00 0.00 2/67 31284
/proc/meminfo: memFree=1805192/2055888 swapFree=4085444/4096564
[pid=31284] ppid=31282 vsize=1488 CPUtime=0
/proc/31284/stat : 31284 (java) R 31282 31284 31238 0 -1 0 60 0 0 0 0 0 0 0 21 0 1 0 252921906 1523712 42 18446744073709551615 134512640 134570276 4294956608 18446744073709551615 11410205 0 0 4096 0 0 0 0 17 1 0 0
/proc/31284/statm: 376 48 38 14 0 7 0

Child status: 30
Real time (s): 0.587054
CPU time (s): 0.817875
CPU user time (s): 0.781881
CPU system time (s): 0.035994
CPU usage (%): 139.319
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node80 on Fri Jun  9 17:07:13 UTC 2006


FILE ID= 50585-1149872833

PBS_JOBID= 384359

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-m50_100_70_70.r.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node80/50585-1149872833/instance-50585-1149872833.opb 207743099
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node80/watcher-50585-1149872833 -o ROOT/results/node80/solver-50585-1149872833 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node80/50585-1149872833/instance-50585-1149872833.opb 207743099

MD5SUM SOLVER= 3cef94aa015dc0dd234d31843a257d70
MD5SUM BENCH=  c2530fca17c8f1e59eb4e770d7ebf727

RANDOM SEED= 207743099


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


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1805400 kB
Buffers:         29676 kB
Cached:         162096 kB
SwapCached:       2436 kB
Active:         101188 kB
Inactive:        99440 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1805400 kB
SwapTotal:     4096564 kB
SwapFree:      4085444 kB
Dirty:             112 kB
Writeback:           0 kB
Mapped:          16648 kB
Slab:            36392 kB
Committed_AS:   597944 kB
PageTables:       1276 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node80 on Fri Jun  9 17:07:14 UTC 2006