Trace number 43005

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 HeuristicsOPT92 1.35979 0.902901

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/primes-dimacs-cnf/normalized-jnh213.opb
MD5SUM0146e39fcd18fa569f99190bc3dd90ba
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark92
Best CPU time to get the best result obtained on this benchmark0.021995
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 92
Optimality of the best value was proved YES
Number of variables200
Total number of constraints900
Number of constraints which are clauses900
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 constraint2
Maximum length of a constraint11
Number of terms in the objective function 200
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 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
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.16	c no version file found!!!
0.16	c sun.arch.data.model	32
0.16	c java.version	1.5.0_06
0.16	c os.name	Linux
0.16	c os.version	2.6.9-34.ELsmp
0.16	c os.arch	i386
0.16	c Free memory 1548419056
0.16	c Max memory 1551040512
0.16	c Total memory 1551040512
0.16	c Number of processors 2
0.22	c Cutting planes based inference
0.22	c --- Begin Solver configuration ---
0.22	c org.sat4j.minisat.uip.FirstUIP@1df073d
0.22	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1546e25
0.22	c org.sat4j.minisat.learning.MiniSATLearning@b66cc
0.22	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.22	c VSIDS like heuristics from MiniSAT using a heap
0.22	c No reason simplification
0.22	c --- End Solver configuration ---
0.22	c solving ROOT/tmp/node90/43005-1149282007/instance-43005-1149282007.opb
0.22	c reading problem ... 
0.45	c ... done. Time 0.229 ms.
0.45	c #vars     200
0.45	c #constraints  900
0.56	c SATISFIABLE
0.56	c OPTIMIZING...
0.56	c Got one! Ellapsed CPU time (in seconds):0.334
0.56	o 95
0.67	c Got one! Ellapsed CPU time (in seconds):0.446
0.67	o 94
0.74	c Got one! Ellapsed CPU time (in seconds):0.517
0.74	o 93
0.77	c Got one! Ellapsed CPU time (in seconds):0.545
0.77	o 92
0.84	c starts		: 5
0.84	c conflicts		: 108
0.84	c decisions		: 266
0.84	c propagations		: 4903
0.84	c inspects		: 21674
0.84	c learnt literals	: 3
0.84	c learnt binary clauses	: 1
0.84	c learnt ternary clauses	: 3
0.84	c learnt clauses	: 104
0.84	c root simplifications	: 0
0.84	c removed literals (reason simplification)	: 0
0.84	c reason swapping (by a shorter reason)	: 0
0.84	c Calls to reduceDB	: 0
0.84	c speed (decisions/second)	: 4222.222222222223
0.84	c non guided choices	0
0.84	s OPTIMUM FOUND
0.84	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 -x30 x31 -x32
0.84	v x33 -x34 -x35 x36 x37 -x38 -x39 x40 -x41 x42 x43 -x44 -x45 x46 -x47 x48 -x49 x50 -x51 x52 x53 -x54 -x55 x56 x57 -x58 -x59 -x60 -x61
0.84	v x62 -x63 x64 -x65 -x66 -x67 x68 -x69 x70 x71 -x72 -x73 -x74 -x75 -x76 x77 -x78 -x79 x80 x81 -x82 -x83 -x84 x85 -x86 x87 -x88 -x89
0.84	v -x90 x91 -x92 -x93 x94 x95 -x96 x97 -x98 -x99 x100 -x101 x102 x103 -x104 x105 -x106 x107 -x108 x109 -x110 x111 -x112 x113 -x114
0.84	v x115 -x116 x117 -x118 x119 -x120 -x121 x122 x123 -x124 x125 -x126 x127 -x128 x129 -x130 x131 -x132 -x133 -x134 x135 -x136 x137
0.84	v -x138 x139 -x140 -x141 x142 x143 -x144 x145 -x146 -x147 x148 x149 -x150 -x151 x152 x153 -x154 -x155 x156 x157 -x158 -x159 x160
0.84	v x161 -x162 -x163 x164 x165 -x166 -x167 -x168 x169 -x170 x171 -x172 x173 -x174 -x175 x176 x177 -x178 x179 -x180 x181 -x182 -x183
0.84	v x184 -x185 x186 -x187 x188 x189 -x190 -x191 x192 -x193 x194 x195 -x196 x197 -x198 -x199 x200
0.84	c objective function=92
0.84	c Total wall clock time (ms): 0.614

Verifier Data (download as text)

OK	92

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node90/watcher-43005-1149282007 -o ROOT/results/node90/solver-43005-1149282007 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node90/43005-1149282007/instance-43005-1149282007.opb 445251611 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.65 0.89 0.88 2/67 17700
/proc/meminfo: memFree=1590240/2055888 swapFree=4085308/4096564
[pid=17700] ppid=17698 vsize=18544 CPUtime=0
/proc/17700/stat : 17700 (runsolver) R 17698 17700 17654 0 -1 4194368 18 0 0 0 0 0 0 0 18 0 1 0 193839760 18989056 280 18446744073709551615 4194304 4262084 548682068944 18446744073709551615 237854323735 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/17700/statm: 4636 280 244 16 0 2626 0

Child status: 30
Real time (s): 0.902901
CPU time (s): 1.35979
CPU user time (s): 1.2958
CPU system time (s): 0.06399
CPU usage (%): 150.603
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node90 on Fri Jun  2 21:00:07 UTC 2006


FILE ID= 43005-1149282007

PBS_JOBID= 306131

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-jnh213.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node90/43005-1149282007/instance-43005-1149282007.opb 445251611
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node90/watcher-43005-1149282007 -o ROOT/results/node90/solver-43005-1149282007 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node90/43005-1149282007/instance-43005-1149282007.opb 445251611

MD5SUM SOLVER= 3cef94aa015dc0dd234d31843a257d70
MD5SUM BENCH=  0146e39fcd18fa569f99190bc3dd90ba

RANDOM SEED= 445251611


/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.227
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.17
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.227
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:      2055888 kB
MemFree:       1590512 kB
Buffers:         29544 kB
Cached:         369088 kB
SwapCached:       2568 kB
Active:          34380 kB
Inactive:       373012 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1590512 kB
SwapTotal:     4096564 kB
SwapFree:      4085308 kB
Dirty:             140 kB
Writeback:           0 kB
Mapped:          16060 kB
Slab:            44788 kB
Committed_AS:   317256 kB
PageTables:       1268 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node90 on Fri Jun  2 21:00:09 UTC 2006