Trace number 1856995

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 NameAnswerobjCPU timeWall clock time
SAT4J Pseudo Resolution 2.1.1OPT5867 1.06684 0.724655

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/
poldner/PB/testset/normalized-6_12.opb
MD5SUMd3b3d1e364c50657a7515a2e4087a65b
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark5867
Best CPU time to get the best result obtained on this benchmark0.014997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 5867
Optimality of the best value was proved YES
Number of variables78
Total number of constraints84
Number of constraints which are clauses72
Number of constraints which are cardinality constraints (but not clauses)12
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint6
Number of terms in the objective function 78
Biggest coefficient in the objective function 2194
Number of bits for the biggest coefficient in the objective function 12
Sum of the numbers in the objective function 39785
Number of bits of the sum of numbers in the objective function 16
Biggest number in a constraint 2194
Number of bits of the biggest number in a constraint 12
Biggest sum of numbers in a constraint 39785
Number of bits of the biggest sum of numbers16
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

0.09/0.13	c SAT4J: a SATisfiability library for Java (c) 2004-2008 Daniel Le Berre
0.09/0.13	c This is free software under the dual EPL/GNU LGPL licenses.
0.09/0.13	c See www.sat4j.org for details.
0.09/0.15	c version 2.1.1.v20090612
0.09/0.15	c sun.arch.data.model	32
0.09/0.15	c java.version	1.6.0_12
0.09/0.15	c os.name	Linux
0.09/0.15	c os.version	2.6.9-22.EL.rootsmp
0.09/0.15	c os.arch	i386
0.09/0.15	c Free memory 1342000320
0.09/0.15	c Max memory 1344274432
0.09/0.15	c Total memory 1344274432
0.09/0.15	c Number of processors 2
0.22/0.21	c Pseudo Boolean Optimization
0.22/0.21	c --- Begin Solver configuration ---
0.22/0.21	c Stops conflict analysis at the first Unique Implication Point
0.22/0.21	c org.sat4j.pb.constraints.CompetResolutionPBMixedHTClauseCardConstrDataStructure@3eca90
0.22/0.21	c Learn all clauses as in MiniSAT
0.22/0.21	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.22/0.21	c VSIDS like heuristics from MiniSAT using a heap phase appearing in latest learned clause taking into account the objective function
0.22/0.21	c Expensive reason simplification
0.22/0.21	c MiniSAT restarts strategy
0.22/0.21	c Memory based learned constraints deletion strategy
0.22/0.21	c timeout=2147483s
0.22/0.21	c DB Simplification allowed=false
0.22/0.21	c --- End Solver configuration ---
0.22/0.21	c solving HOME/instance-1856995-1244929778.opb
0.22/0.21	c reading problem ... 
0.22/0.26	c ... done. Wall clock time 0.044s.
0.22/0.26	c #vars     78
0.22/0.26	c #constraints  96
0.22/0.26	c constraints type 
0.22/0.26	c org.sat4j.minisat.constraints.card.MinWatchCard => 12
0.22/0.26	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 72
0.22/0.26	c org.sat4j.minisat.constraints.cnf.OriginalHTClause => 12
0.22/0.27	c SATISFIABLE
0.22/0.27	c OPTIMIZING...
0.22/0.27	c Got one! Elapsed wall clock time (in seconds):0.057
0.22/0.27	o 6639
0.34/0.31	c Got one! Elapsed wall clock time (in seconds):0.094
0.34/0.31	o 6553
0.34/0.32	c Got one! Elapsed wall clock time (in seconds):0.102
0.34/0.32	o 5867
0.88/0.68	c starts		: 8
0.88/0.68	c conflicts		: 969
0.88/0.68	c decisions		: 1090
0.88/0.68	c propagations		: 10671
0.88/0.68	c inspects		: 44378
0.88/0.68	c learnt literals	: 8
0.88/0.68	c learnt binary clauses	: 17
0.88/0.68	c learnt ternary clauses	: 23
0.88/0.68	c learnt clauses	: 960
0.88/0.68	c ignored clauses	: 0
0.88/0.68	c root simplifications	: 0
0.88/0.68	c removed literals (reason simplification)	: 1708
0.88/0.68	c reason swapping (by a shorter reason)	: 0
0.88/0.68	c Calls to reduceDB	: 0
0.88/0.68	c speed (assignments/second)	: 29396.694214876035
0.88/0.68	c non guided choices	0
0.88/0.68	c learnt constraints type 
0.88/0.68	c constraints type 
0.88/0.68	c org.sat4j.minisat.constraints.card.MinWatchCard => 12
0.88/0.68	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 72
0.88/0.68	c org.sat4j.pb.constraints.pb.MaxWatchPb => 0
0.88/0.68	c org.sat4j.minisat.constraints.cnf.OriginalHTClause => 12
0.88/0.68	s OPTIMUM FOUND
0.88/0.68	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 
0.88/0.68	c objective function=5867
0.88/0.68	c Total wall clock time (in seconds): 0.468

Verifier Data

OK	5867

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1856995-1244929778/watcher-1856995-1244929778 -o /tmp/evaluation-result-1856995-1244929778/solver-1856995-1244929778 -C 1800 -W 2000 -M 1800 java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar HOME/instance-1856995-1244929778.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: 1.00 1.00 1.00 3/64 17130
/proc/meminfo: memFree=1397104/2055920 swapFree=4191900/4192956
[pid=17130] ppid=17128 vsize=152 CPUtime=0
/proc/17130/stat : 17130 (java) R 17128 17130 16544 0 -1 0 204 0 0 0 0 0 0 0 18 0 1 0 160575013 155648 26 1992294400 134512640 134550932 4294956016 18446744073709551615 8605995 0 0 4096 0 0 0 0 17 1 0 0
/proc/17130/statm: 38 26 19 9 0 4 0

[startup+0.073073 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 17130
/proc/meminfo: memFree=1397104/2055920 swapFree=4191900/4192956
[pid=17130] ppid=17128 vsize=1470220 CPUtime=0.06
/proc/17130/stat : 17130 (java) S 17128 17130 16544 0 -1 0 3421 0 1 0 4 2 0 0 18 0 7 0 160575013 1505505280 3166 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800971 18446744073709551615 0 0 17 1 0 0
/proc/17130/statm: 367555 3166 1036 9 0 364906 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 1470220

[startup+0.102076 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 17130
/proc/meminfo: memFree=1397104/2055920 swapFree=4191900/4192956
[pid=17130] ppid=17128 vsize=1472584 CPUtime=0.09
/proc/17130/stat : 17130 (java) S 17128 17130 16544 0 -1 0 3655 0 1 0 7 2 0 0 18 0 12 0 160575013 1507926016 3398 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17130/statm: 368146 3398 1069 9 0 365494 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1472584

[startup+0.302095 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 17130
/proc/meminfo: memFree=1397104/2055920 swapFree=4191900/4192956
[pid=17130] ppid=17128 vsize=1475716 CPUtime=0.34
/proc/17130/stat : 17130 (java) S 17128 17130 16544 0 -1 0 5151 0 1 0 30 4 0 0 18 0 13 0 160575013 1511133184 4880 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17130/statm: 368929 4880 1344 9 0 366272 0
Current children cumulated CPU time (s) 0.34
Current children cumulated vsize (KiB) 1475716

[startup+0.702137 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 17130
/proc/meminfo: memFree=1397104/2055920 swapFree=4191900/4192956
[pid=17130] ppid=17128 vsize=1478280 CPUtime=1.06
/proc/17130/stat : 17130 (java) S 17128 17130 16544 0 -1 0 6814 0 1 0 101 5 0 0 18 0 13 0 160575013 1513758720 5900 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/17130/statm: 369570 5900 1409 9 0 366913 0
Current children cumulated CPU time (s) 1.06
Current children cumulated vsize (KiB) 1478280

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

Child status: 30
Real time (s): 0.724655
CPU time (s): 1.06684
CPU user time (s): 1.01085
CPU system time (s): 0.055991
CPU usage (%): 147.22
Max. virtual memory (cumulated for all children) (KiB): 1478280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.01085
system time used= 0.055991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6818
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= 213
involuntary context switches= 180

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data

Begin job on node38 at 2009-06-13 23:49:38
IDJOB=1856995
IDBENCH=24967
IDSOLVER=682
FILE ID=node38/1856995-1244929778
PBS_JOBID= 9354654
Free space on /tmp= 66280 MiB

SOLVER NAME= SAT4J Pseudo Resolution 2.1.1
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-6_12.opb
COMMAND LINE= java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1856995-1244929778/watcher-1856995-1244929778 -o /tmp/evaluation-result-1856995-1244929778/solver-1856995-1244929778 -C 1800 -W 2000 -M 1800  java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar HOME/instance-1856995-1244929778.opb

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

MD5SUM BENCH= d3b3d1e364c50657a7515a2e4087a65b
RANDOM SEED=43219439

node38.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.232
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.232
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:       1397584 kB
Buffers:         65744 kB
Cached:         498268 kB
SwapCached:        592 kB
Active:          35932 kB
Inactive:       541676 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1397584 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:             444 kB
Writeback:           0 kB
Mapped:          22516 kB
Slab:            66580 kB
Committed_AS:   118472 kB
PageTables:       1464 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66280 MiB
End job on node38 at 2009-06-13 23:49:39