Trace number 44015

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.2OPT7985 8.32373 7.20623

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/
MIPLIB/miplib/normalized-reduced-mps-v2-20-10-p0291.opb
MD5SUM95e4efc01e56e7c627bbc0cc1139ffbe
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark7985
Best CPU time to get the best result obtained on this benchmark0.055991
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 7985
Optimality of the best value was proved YES
Number of variables290
Total number of constraints205
Number of constraints which are clauses189
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints14
Minimum length of a constraint2
Maximum length of a constraint53
Number of terms in the objective function 288
Biggest coefficient in the objective function 61096
Number of bits for the biggest coefficient in the objective function 16
Sum of the numbers in the objective function 524351
Number of bits of the sum of numbers in the objective function 20
Biggest number in a constraint 61096
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 524351
Number of bits of the biggest sum of numbers20
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.20	c Cutting planes based inference
0.20	c --- Begin Solver configuration ---
0.20	c org.sat4j.minisat.uip.FirstUIP@1037c71
0.20	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@1df073d
0.20	c org.sat4j.minisat.learning.MiniSATLearning@1546e25
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/node78/44015-1149351397/instance-44015-1149351397.opb
0.20	c reading problem ... 
0.33	c ... done. Time 0.129 ms.
0.33	c #vars     290
0.33	c #constraints  205
0.34	c SATISFIABLE
0.34	c OPTIMIZING...
0.34	c Got one! Ellapsed CPU time (in seconds):0.142
0.36	o 59612
0.70	c Got one! Ellapsed CPU time (in seconds):0.497
0.70	o 59544
0.90	c Got one! Ellapsed CPU time (in seconds):0.699
0.90	o 59027
0.92	c Got one! Ellapsed CPU time (in seconds):0.724
0.92	o 58681
1.14	c Got one! Ellapsed CPU time (in seconds):0.935
1.14	o 52752
1.22	c Got one! Ellapsed CPU time (in seconds):1.022
1.22	o 52173
1.61	c Got one! Ellapsed CPU time (in seconds):1.407
1.61	o 39722
1.65	c Got one! Ellapsed CPU time (in seconds):1.449
1.65	o 33623
1.70	c Got one! Ellapsed CPU time (in seconds):1.499
1.70	o 26993
1.72	c Got one! Ellapsed CPU time (in seconds):1.521
1.72	o 19624
1.82	c Got one! Ellapsed CPU time (in seconds):1.617
1.82	o 12260
1.82	c Got one! Ellapsed CPU time (in seconds):1.62
1.82	o 10719
1.83	c Got one! Ellapsed CPU time (in seconds):1.635
1.83	o 10472
1.94	c Got one! Ellapsed CPU time (in seconds):1.738
1.94	o 10468
1.98	c Got one! Ellapsed CPU time (in seconds):1.777
1.98	o 8776
2.39	c Got one! Ellapsed CPU time (in seconds):2.187
2.39	o 8737
2.67	c Got one! Ellapsed CPU time (in seconds):2.475
2.68	o 8524
2.98	c Got one! Ellapsed CPU time (in seconds):2.779
2.98	o 8423
3.53	c Got one! Ellapsed CPU time (in seconds):3.332
3.53	o 8357
3.92	c Got one! Ellapsed CPU time (in seconds):3.724
3.92	o 8334
4.52	c Got one! Ellapsed CPU time (in seconds):4.325
4.52	o 8231
4.68	c Got one! Ellapsed CPU time (in seconds):4.476
4.68	o 8107
6.09	c Got one! Ellapsed CPU time (in seconds):5.889
6.09	o 8024
6.49	c Got one! Ellapsed CPU time (in seconds):6.289
6.49	o 7985
7.13	c starts		: 25
7.13	c conflicts		: 225
7.13	c decisions		: 6740
7.13	c propagations		: 15037
7.13	c inspects		: 99527
7.13	c learnt literals	: 0
7.13	c learnt binary clauses	: 0
7.13	c learnt ternary clauses	: 0
7.13	c learnt clauses	: 224
7.13	c root simplifications	: 0
7.13	c removed literals (reason simplification)	: 0
7.13	c reason swapping (by a shorter reason)	: 0
7.13	c Calls to reduceDB	: 0
7.13	c speed (decisions/second)	: 10531.25
7.13	c non guided choices	1448
7.13	s OPTIMUM FOUND
7.13	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
7.13	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
7.13	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
7.13	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104
7.13	v -x105 -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125
7.13	v -x126 -x127 -x128 -x129 x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146
7.13	v -x147 -x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167
7.13	v -x168 -x169 -x170 -x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 -x183 -x184 -x185 -x186 -x187 -x188
7.13	v -x189 -x190 -x191 -x192 -x193 -x194 -x195 -x196 -x197 -x198 -x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 -x209
7.13	v -x210 -x211 -x212 -x213 -x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 -x222 -x223 -x224 -x225 -x226 -x227 -x228 -x229 -x230
7.13	v -x231 -x232 -x233 -x234 -x235 -x236 -x237 -x238 -x239 -x240 -x241 x242 x243 -x244 -x245 -x246 -x247 -x248 -x249 x250 -x251
7.13	v x252 x253 -x254 -x255 -x256 -x257 -x258 -x259 -x260 -x261 -x262 x263 -x264 x265 x266 -x267 -x268 -x269 -x270 -x271 -x272 -x273
7.13	v -x274 -x275 -x276 -x277 -x278 -x279 -x280 -x281 -x282 -x283 -x284 -x285 x286 -x287 -x288 -x289 -x290
7.13	c objective function=7985
7.13	c Total wall clock time (ms): 6.932

Verifier Data (download as text)

OK	7985

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/node78/watcher-44015-1149351397 -o ROOT/results/node78/solver-44015-1149351397 -C 1800 -M 1800 -S 64 java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node78/44015-1149351397/instance-44015-1149351397.opb 599776747 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.75 0.91 0.96 2/67 19758
/proc/meminfo: memFree=1738280/2055892 swapFree=4085732/4096564
[pid=19758] ppid=19756 vsize=164 CPUtime=0
/proc/19758/stat : 19758 (java) R 19756 19758 19712 0 -1 0 26 0 0 0 0 0 0 0 19 0 1 0 200168520 167936 9 18446744073709551615 134512640 134570276 4294956624 18446744073709551615 11461904 0 0 4096 0 0 0 0 17 1 0 0
/proc/19758/statm: 42 18 13 14 0 2 0

Child status: 30
Real time (s): 7.20623
CPU time (s): 8.32373
CPU user time (s): 8.06177
CPU system time (s): 0.26196
CPU usage (%): 115.508
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node78 on Sat Jun  3 16:16:37 UTC 2006


FILE ID= 44015-1149351397

PBS_JOBID= 311012

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/MIPLIB/miplib/normalized-reduced-mps-v2-20-10-p0291.opb
COMMAND LINE= java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node78/44015-1149351397/instance-44015-1149351397.opb 599776747
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node78/watcher-44015-1149351397 -o ROOT/results/node78/solver-44015-1149351397 -C 1800 -M 1800 -S 64  java -server -Xms1500M -Xmx1500M -jar ROOT/solvers/PB/PB06final/user5/sat4jPseudoPlus.jar ROOT/tmp/node78/44015-1149351397/instance-44015-1149351397.opb 599776747

MD5SUM SOLVER= e9637a7554f3ecdf74c1815f89d00213
MD5SUM BENCH=  95e4efc01e56e7c627bbc0cc1139ffbe

RANDOM SEED= 599776747


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1738680 kB
Buffers:         15380 kB
Cached:         243160 kB
SwapCached:       2512 kB
Active:          40932 kB
Inactive:       226388 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1738680 kB
SwapTotal:     4096564 kB
SwapFree:      4085732 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          15196 kB
Slab:            36420 kB
Committed_AS:   354332 kB
PageTables:       1420 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node78 on Sat Jun  3 16:16:44 UTC 2006