Trace number 2659739

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
SAT4J PB Resolution 2.2.0 2010-05-26OPT100 0.6509 0.490184

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-aim-100-6_0-yes1-1.opb
MD5SUMddad9041bd4289151f7a18bb8ca7a5ec
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark100
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 100
Optimality of the best value was proved YES
Number of variables200
Total number of constraints700
Number of constraints which are clauses697
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints3
Minimum length of a constraint2
Maximum length of a constraint3
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 2
Number of bits of the biggest number in a constraint 2
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

Solver Data 

0.08/0.14	c SAT4J: a SATisfiability library for Java (c) 2004-2010 Daniel Le Berre
0.08/0.14	c This is free software under the dual EPL/GNU LGPL licenses.
0.08/0.14	c See www.sat4j.org for details.
0.08/0.15	c version 2.2.0.v20100526
0.08/0.15	c java.runtime.name	Java(TM) SE Runtime Environment
0.08/0.15	c java.vm.name		Java HotSpot(TM) Server VM
0.08/0.15	c java.vm.version	11.2-b01
0.08/0.15	c java.vm.vendor	Sun Microsystems Inc.
0.08/0.15	c sun.arch.data.model	32
0.08/0.15	c java.version		1.6.0_12
0.08/0.15	c os.name		Linux
0.08/0.15	c os.version		2.6.18-164.el5
0.08/0.15	c os.arch		i386
0.08/0.15	c Free memory 		1393557488
0.08/0.15	c Max memory 		1395916800
0.08/0.15	c Total memory 		1395916800
0.08/0.15	c Number of processors 	2
0.25/0.21	c Pseudo Boolean Optimization
0.25/0.21	c --- Begin Solver configuration ---
0.25/0.21	c Stops conflict analysis at the first Unique Implication Point
0.25/0.21	c org.sat4j.pb.constraints.CompetResolutionPBMixedWLClauseCardConstrDataStructure@64dc11
0.25/0.21	c Learn all clauses as in MiniSAT
0.25/0.21	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.25/0.21	c VSIDS like heuristics from MiniSAT using a heap lightweight component caching from RSAT taking into account the objective function
0.25/0.21	c Expensive reason simplification
0.25/0.21	c Armin Biere (Picosat) restarts strategy
0.25/0.21	c Glucose learned constraints deletion strategy
0.25/0.21	c timeout=2147483s
0.25/0.21	c DB Simplification allowed=false
0.25/0.21	c --- End Solver configuration ---
0.25/0.21	c solving HOME/instance-2659739-1276465380.opb
0.25/0.21	c reading problem ... 
0.35/0.39	c ... done. Wall clock time 0.183s.
0.35/0.39	c #vars     200
0.35/0.39	c #constraints  700
0.35/0.39	c constraints type 
0.35/0.39	c org.sat4j.minisat.constraints.cnf.OriginalWLClause => 597
0.35/0.39	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 103
0.53/0.42	c SATISFIABLE
0.53/0.42	c OPTIMIZING...
0.53/0.42	c Got one! Elapsed wall clock time (in seconds):0.218
0.53/0.42	o 100
0.53/0.46	c starts		: 2
0.53/0.46	c conflicts		: 37
0.53/0.46	c decisions		: 59
0.53/0.46	c propagations		: 1301
0.53/0.46	c inspects		: 4339
0.53/0.46	c learnt literals	: 5
0.53/0.46	c learnt binary clauses	: 17
0.53/0.46	c learnt ternary clauses	: 10
0.53/0.46	c learnt clauses	: 31
0.53/0.46	c ignored clauses	: 0
0.53/0.46	c root simplifications	: 0
0.53/0.46	c removed literals (reason simplification)	: 9
0.53/0.46	c reason swapping (by a shorter reason)	: 0
0.53/0.46	c Calls to reduceDB	: 0
0.53/0.46	c number of reductions to clauses (during analyze)	: 0
0.53/0.46	c number of learned constraints concerned by reduction	: 0
0.53/0.46	c number of learning phase by resolution	: 0
0.53/0.46	c number of learning phase by cutting planes	: 0
0.53/0.46	c speed (assignments/second)	: 40656.25
0.53/0.46	c non guided choices	0
0.53/0.46	c learnt constraints type 
0.53/0.46	c constraints type 
0.53/0.46	c org.sat4j.minisat.constraints.cnf.OriginalWLClause => 597
0.53/0.46	c org.sat4j.minisat.constraints.card.MinWatchCard => 0
0.53/0.46	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 103
0.53/0.46	s OPTIMUM FOUND
0.53/0.46	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 -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 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 -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 -x115 x116 x117 -x118 -x119 x120 -x121 x122 x123 -x124 -x125 x126 x127 -x128 -x129 x130 -x131 x132 -x133 x134 x135 -x136 -x137 x138 -x139 x140 x141 -x142 x143 -x144 x145 -x146 -x147 x148 x149 -x150 x151 -x152 x153 -x154 x155 -x156 x157 -x158 -x159 x160 -x161 x162 -x163 x164 -x165 x166 x167 -x168 x169 -x170 -x171 x172 x173 -x174 x175 -x176 x177 -x178 x179 -x180 x181 -x182 x183 -x184 x185 -x186 -x187 x188 -x189 x190 x191 -x192 -x193 x194 x195 -x196 -x197 x198 -x199 x200 
0.53/0.46	c objective function=100
0.53/0.46	c Total wall clock time (in seconds): 0.257

Verifier Data 

OK	100

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2659739-1276465380/watcher-2659739-1276465380 -o /tmp/evaluation-result-2659739-1276465380/solver-2659739-1276465380 -C 1800 -W 2000 -M 1800 java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar HOME/instance-2659739-1276465380.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.85 0.97 0.99 3/106 25692
/proc/meminfo: memFree=1801352/2059040 swapFree=4140084/4192956
[pid=25692] ppid=25690 vsize=1832 CPUtime=0
/proc/25692/stat : 25692 (java6) S 25690 25692 25586 0 -1 4194304 244 0 0 0 0 0 0 0 19 0 1 0 22139412 1875968 148 1992294400 134512640 134550932 4290181376 18446744073709551615 4294960144 0 2147483391 4096 0 18446744071699387582 0 0 17 1 0 0 0
/proc/25692/statm: 458 148 111 10 0 63 0

[startup+0.0541601 s]
/proc/loadavg: 0.85 0.97 0.99 3/106 25692
/proc/meminfo: memFree=1801352/2059040 swapFree=4140084/4192956
[pid=25692] ppid=25690 vsize=1521664 CPUtime=0.04
/proc/25692/stat : 25692 (java) S 25690 25692 25586 0 -1 4202496 3539 0 1 0 2 2 0 0 18 0 7 0 22139412 1558183936 2981 1992294400 134512640 134550932 4290472608 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 0 0 0 0
/proc/25692/statm: 380416 2981 1007 10 0 377726 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 1521664

[startup+0.101165 s]
/proc/loadavg: 0.85 0.97 0.99 3/106 25692
/proc/meminfo: memFree=1801352/2059040 swapFree=4140084/4192956
[pid=25692] ppid=25690 vsize=1524184 CPUtime=0.08
/proc/25692/stat : 25692 (java) S 25690 25692 25586 0 -1 4202496 3959 0 1 0 6 2 0 0 18 0 12 0 22139412 1560764416 3399 1992294400 134512640 134550932 4290472608 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0 0
/proc/25692/statm: 381046 3399 1076 10 0 378348 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1524184

[startup+0.301201 s]
/proc/loadavg: 0.85 0.97 0.99 3/106 25692
/proc/meminfo: memFree=1801352/2059040 swapFree=4140084/4192956
[pid=25692] ppid=25690 vsize=1526224 CPUtime=0.35
/proc/25692/stat : 25692 (java) S 25690 25692 25586 0 -1 4202496 5286 0 1 0 32 3 0 0 18 0 12 0 22139412 1562853376 4724 1992294400 134512640 134550932 4290472608 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0 0
/proc/25692/statm: 381556 4724 1361 10 0 378858 0
Current children cumulated CPU time (s) 0.35
Current children cumulated vsize (KiB) 1526224

Solver just ended. Dumping a history of the last processes samples

[startup+0.401219 s]
/proc/loadavg: 0.85 0.97 0.99 3/106 25692
/proc/meminfo: memFree=1801352/2059040 swapFree=4140084/4192956
[pid=25692] ppid=25690 vsize=1526532 CPUtime=0.53
/proc/25692/stat : 25692 (java) S 25690 25692 25586 0 -1 4202496 5643 0 1 0 50 3 0 0 18 0 12 0 22139412 1563168768 5081 1992294400 134512640 134550932 4290472608 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0 0
/proc/25692/statm: 381633 5082 1383 10 0 378935 0
Current children cumulated CPU time (s) 0.53
Current children cumulated vsize (KiB) 1526532

Child status: 30
Real time (s): 0.490184
CPU time (s): 0.6509
CPU user time (s): 0.608907
CPU system time (s): 0.041993
CPU usage (%): 132.787
Max. virtual memory (cumulated for all children) (KiB): 1526532

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.608907
system time used= 0.041993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5934
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 151
involuntary context switches= 82

runsolver used 0.003999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node014 at 2010-06-13 23:43:00
IDJOB=2659739
IDBENCH=2182
IDSOLVER=1164
FILE ID=node014/2659739-1276465380
PBS_JOBID= 11173364
Free space on /tmp= 62464 MiB

SOLVER NAME= SAT4J PB Resolution 2.2.0 2010-05-26
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-aim-100-6_0-yes1-1.opb
COMMAND LINE= java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2659739-1276465380/watcher-2659739-1276465380 -o /tmp/evaluation-result-2659739-1276465380/solver-2659739-1276465380 -C 1800 -W 2000 -M 1800  java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar HOME/instance-2659739-1276465380.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= ddad9041bd4289151f7a18bb8ca7a5ec
RANDOM SEED=845707718

node014.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.258
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.51
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.258
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1801748 kB
Buffers:         41968 kB
Cached:         124916 kB
SwapCached:       7288 kB
Active:          97224 kB
Inactive:        83768 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1801748 kB
SwapTotal:     4192956 kB
SwapFree:      4140084 kB
Dirty:             388 kB
Writeback:           4 kB
AnonPages:       11756 kB
Mapped:          13088 kB
Slab:            54292 kB
PageTables:       4060 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183392 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62464 MiB
End job on node014 at 2010-06-13 23:43:01