Trace number 43060

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 HeuristicsOPT304 1.14482 0.739219

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/
~walser/benchmarks/course-ass/normalized-ss97-6.opb
MD5SUMdcfce19ac0444148b26b7675e35c76bc
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark304
Best CPU time to get the best result obtained on this benchmark0.010997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 304
Optimality of the best value was proved YES
Number of variables257
Total number of constraints97
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)97
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint44
Number of terms in the objective function 173
Biggest coefficient in the objective function 100
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 8448
Number of bits of the sum of numbers in the objective function 14
Biggest number in a constraint 100
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 8448
Number of bits of the biggest sum of numbers14
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.14	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.14	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.14	c no version file found!!!
0.14	c sun.arch.data.model	32
0.14	c java.version	1.5.0_06
0.14	c os.name	Linux
0.14	c os.version	2.6.9-22.EL.rootsmp
0.14	c os.arch	i386
0.14	c Free memory 1548419056
0.14	c Max memory 1551040512
0.14	c Total memory 1551040512
0.14	c Number of processors 2
0.20	c Cutting planes based inference
0.20	c --- Begin Solver configuration ---
0.20	c org.sat4j.minisat.uip.FirstUIP@1df073d
0.20	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1546e25
0.20	c org.sat4j.minisat.learning.MiniSATLearning@b66cc
0.20	c conflictBoundIncFactor=1.5 learntBoundIncFactor=1.1 initLearntBoundConstraintFactor=10000.0 initConflictBound=100 
0.20	c VSIDS like heuristics from MiniSAT using a heap
0.20	c No reason simplification
0.20	c --- End Solver configuration ---
0.20	c solving ROOT/tmp/node4/43060-1149291096/instance-43060-1149291096.opb
0.20	c reading problem ... 
0.31	c ... done. Time 0.11 ms.
0.31	c #vars     257
0.31	c #constraints  180
0.33	c SATISFIABLE
0.33	c OPTIMIZING...
0.33	c Got one! Ellapsed CPU time (in seconds):0.13
0.34	o 305
0.58	c Got one! Ellapsed CPU time (in seconds):0.382
0.58	o 304
0.71	c starts		: 3
0.71	c conflicts		: 49
0.71	c decisions		: 370
0.71	c propagations		: 1091
0.71	c inspects		: 1440
0.71	c learnt literals	: 0
0.71	c learnt binary clauses	: 0
0.71	c learnt ternary clauses	: 0
0.71	c learnt clauses	: 48
0.71	c root simplifications	: 0
0.71	c removed literals (reason simplification)	: 0
0.71	c reason swapping (by a shorter reason)	: 0
0.71	c Calls to reduceDB	: 0
0.71	c speed (decisions/second)	: 3032.786885245902
0.71	c non guided choices	26
0.71	s OPTIMUM FOUND
0.71	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
0.71	v -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 -x57 -x58
0.71	v -x59 -x60 -x61 x62 x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84
0.71	v x85 -x86 -x87 -x88 x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 x100 -x101 -x102 -x103 x104 -x105 -x106 -x107 -x108
0.71	v -x109 -x110 -x111 x112 -x113 -x114 -x115 -x116 -x117 x118 x119 -x120 x121 x122 -x123 -x124 x125 -x126 x127 -x128 -x129 x130
0.71	v x131 x132 -x133 x134 x135 -x136 x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 -x148 x149 -x150 -x151 -x152
0.71	v x153 -x154 x155 -x156 -x157 x158 -x159 -x160 x161 -x162 -x163 x164 -x165 -x166 x167 x168 -x169 -x170 -x171 x172 -x173 -x174
0.71	v -x175 -x176 -x177 -x178 -x179 x180 x181 x182 -x183 x184 x185 -x186 x187 x188 x189 -x190 -x191 x192 x193 x194 x195 x196 -x197
0.71	v x198 x199 -x200 x201 -x202 -x203 -x204 x205 x206 -x207 -x208 -x209 -x210 -x211 -x212 -x213 -x214 x215 -x216 -x217 x218 x219
0.71	v -x220 -x221 -x222 x223 -x224 -x225 x226 -x227 -x228 -x229 x230 x231 -x232 -x233 -x234 -x235 -x236 x237 -x238 -x239 x240 -x241
0.71	v x242 x243 x244 -x245 -x246 x247 x248 x249 x250 x251 x252 x253 x254 -x255 x256 x257
0.71	c objective function=304
0.71	c Total wall clock time (ms): 0.513

Verifier Data (download as text)

OK	304

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.94 0.90 2/64 7299
/proc/meminfo: memFree=1799400/2055920 swapFree=4181448/4192956
[pid=7299] ppid=7297 vsize=172 CPUtime=0
/proc/7299/stat : 7299 (java) R 7297 7299 7253 0 -1 0 201 0 0 0 0 0 0 0 19 0 1 0 194771530 176128 24 18446744073709551615 134512640 134570276 4294956464 18446744073709551615 10588459 0 0 4096 0 0 0 0 17 1 0 0
/proc/7299/statm: 43 24 18 14 0 3 0

Child status: 30
Real time (s): 0.739219
CPU time (s): 1.14482
CPU user time (s): 1.09483
CPU system time (s): 0.049992
CPU usage (%): 154.87
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node4 on Fri Jun  2 23:31:36 UTC 2006


FILE ID= 43060-1149291096

PBS_JOBID= 306857

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/course-ass/normalized-ss97-6.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node4/43060-1149291096/instance-43060-1149291096.opb 858747677
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-43060-1149291096 -o ROOT/results/node4/solver-43060-1149291096 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoHeuristics.jar ROOT/tmp/node4/43060-1149291096/instance-43060-1149291096.opb 858747677

MD5SUM SOLVER= 3cef94aa015dc0dd234d31843a257d70
MD5SUM BENCH=  dcfce19ac0444148b26b7675e35c76bc

RANDOM SEED= 858747677


/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.236
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.236
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:       1799608 kB
Buffers:         20996 kB
Cached:         175116 kB
SwapCached:       3264 kB
Active:          45800 kB
Inactive:       159120 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1799608 kB
SwapTotal:     4192956 kB
SwapFree:      4181448 kB
Dirty:             304 kB
Writeback:           0 kB
Mapped:          14816 kB
Slab:            37336 kB
Committed_AS:   286844 kB
PageTables:       1500 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node4 on Fri Jun  2 23:31:37 UTC 2006