Trace number 1859641

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.1OPT46877 0.315951 0.303879

General information on the benchmark

Name/OPT-BIGINT-LIN/aries-da_nrp/
normalized-aries-da_network_20_2__17_12.opb
MD5SUMea761b6b937db07d13aa1ca1725d4f7c
Bench CategoryOPT-BIGINT-LIN (optimisation, big integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark46877
Best CPU time to get the best result obtained on this benchmark0.315951
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables58
Total number of constraints20
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints18
Minimum length of a constraint2
Maximum length of a constraint9
Number of terms in the objective function 40
Biggest coefficient in the objective function 94409
Number of bits for the biggest coefficient in the objective function 17
Sum of the numbers in the objective function 1744562
Number of bits of the sum of numbers in the objective function 21
Biggest number in a constraint 94409
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 1744562
Number of bits of the biggest sum of numbers21
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.13	c SAT4J: a SATisfiability library for Java (c) 2004-2008 Daniel Le Berre
0.08/0.13	c This is free software under the dual EPL/GNU LGPL licenses.
0.08/0.13	c See www.sat4j.org for details.
0.08/0.14	c version 2.1.1.v20090612
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.9-22.EL.rootsmp
0.08/0.15	c os.arch	i386
0.08/0.15	c Free memory 1342000320
0.08/0.15	c Max memory 1344274432
0.08/0.15	c Total memory 1344274432
0.08/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-1859641-1244974482.opb
0.22/0.21	c reading problem ... 
0.22/0.24	c ... done. Wall clock time 0.033s.
0.22/0.24	c #vars     58
0.22/0.24	c #constraints  40
0.22/0.24	c constraints type 
0.22/0.24	c org.sat4j.minisat.constraints.card.MinWatchCard => 1
0.22/0.24	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 2
0.22/0.24	c org.sat4j.pb.constraints.pb.MaxWatchPb => 36
0.22/0.24	c org.sat4j.minisat.constraints.cnf.OriginalHTClause => 1
0.22/0.25	c SATISFIABLE
0.22/0.25	c OPTIMIZING...
0.22/0.25	c Got one! Elapsed wall clock time (in seconds):0.044
0.22/0.25	o 46877
0.22/0.26	c starts		: 1
0.22/0.26	c conflicts		: 0
0.22/0.26	c decisions		: 22
0.22/0.26	c propagations		: 100
0.22/0.26	c inspects		: 172
0.22/0.26	c learnt literals	: 0
0.22/0.26	c learnt binary clauses	: 0
0.22/0.26	c learnt ternary clauses	: 0
0.22/0.26	c learnt clauses	: 0
0.22/0.26	c ignored clauses	: 0
0.22/0.26	c root simplifications	: 0
0.22/0.26	c removed literals (reason simplification)	: 0
0.22/0.26	c reason swapping (by a shorter reason)	: 0
0.22/0.26	c Calls to reduceDB	: 0
0.22/0.26	c speed (assignments/second)	: 25000.0
0.22/0.26	c non guided choices	0
0.22/0.26	c learnt constraints type 
0.22/0.26	c constraints type 
0.22/0.26	c org.sat4j.minisat.constraints.card.MinWatchCard => 1
0.22/0.26	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 2
0.22/0.26	c org.sat4j.pb.constraints.pb.MaxWatchPb => 36
0.22/0.26	c org.sat4j.minisat.constraints.cnf.OriginalHTClause => 1
0.22/0.26	s OPTIMUM FOUND
0.22/0.26	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 
0.22/0.26	c objective function=46877
0.22/0.26	c Total wall clock time (in seconds): 0.051

Verifier Data 

OK	46877

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1859641-1244974482/watcher-1859641-1244974482 -o /tmp/evaluation-result-1859641-1244974482/solver-1859641-1244974482 -C 1800 -W 2000 -M 1800 java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar HOME/instance-1859641-1244974482.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.92 0.98 0.99 3/64 18762
/proc/meminfo: memFree=1299568/2055920 swapFree=4191900/4192956
[pid=18762] ppid=18760 vsize=152 CPUtime=0
/proc/18762/stat : 18762 (java6) R 18760 18762 18514 0 -1 0 41 0 0 0 0 0 0 0 21 0 1 0 165048850 155648 26 1992294400 134512640 134550932 4294956176 18446744073709551615 8663339 0 0 4096 0 0 0 0 17 1 0 0
/proc/18762/statm: 38 26 19 9 0 4 0

[startup+0.09293 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 18762
/proc/meminfo: memFree=1299568/2055920 swapFree=4191900/4192956
[pid=18762] ppid=18760 vsize=1472584 CPUtime=0.08
/proc/18762/stat : 18762 (java) S 18760 18762 18514 0 -1 0 3584 0 1 0 6 2 0 0 18 0 12 0 165048850 1507926016 3327 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/18762/statm: 368146 3327 1066 9 0 365494 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1472584

[startup+0.101929 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 18762
/proc/meminfo: memFree=1299568/2055920 swapFree=4191900/4192956
[pid=18762] ppid=18760 vsize=1472584 CPUtime=0.08
/proc/18762/stat : 18762 (java) S 18760 18762 18514 0 -1 0 3638 0 1 0 6 2 0 0 18 0 12 0 165048850 1507926016 3381 1992294400 134512640 134550932 4294956016 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/18762/statm: 368146 3381 1068 9 0 365494 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1472584

[startup+0.302028 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 18762
/proc/meminfo: memFree=1299568/2055920 swapFree=4191900/4192956
[pid=18762] ppid=18760 vsize=0 CPUtime=0.31
/proc/18762/stat : 18762 (java) Z 18760 18762 18514 0 -1 1036 5023 0 1 0 28 3 0 0 16 0 2 0 165048850 0 0 1992294400 0 0 0 0 0 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/18762/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0.31
Current children cumulated vsize (KiB) 0

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

Child status: 30
Real time (s): 0.303879
CPU time (s): 0.315951
CPU user time (s): 0.280957
CPU system time (s): 0.034994
CPU usage (%): 103.973
Max. virtual memory (cumulated for all children) (KiB): 1475004

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.280957
system time used= 0.034994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5023
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= 93
involuntary context switches= 85

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node9 at 2009-06-14 12:14:42
IDJOB=1859641
IDBENCH=71869
IDSOLVER=682
FILE ID=node9/1859641-1244974482
PBS_JOBID= 9355049
Free space on /tmp= 66200 MiB

SOLVER NAME= SAT4J Pseudo Resolution 2.1.1
BENCH NAME= PB09/normalized-PB09/OPT-BIGINT-LIN/aries-da_nrp/normalized-aries-da_network_20_2__17_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-1859641-1244974482/watcher-1859641-1244974482 -o /tmp/evaluation-result-1859641-1244974482/solver-1859641-1244974482 -C 1800 -W 2000 -M 1800  java6 -server -Xms1300m -Xmx1300m -jar HOME/org.sat4j.pb.jar HOME/instance-1859641-1244974482.opb

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

MD5SUM BENCH= ea761b6b937db07d13aa1ca1725d4f7c
RANDOM SEED=1503769777

node9.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.231
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.231
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:       1300048 kB
Buffers:         77004 kB
Cached:         590292 kB
SwapCached:        260 kB
Active:         118284 kB
Inactive:       561772 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1300048 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:          21996 kB
Slab:            61820 kB
Committed_AS:   133552 kB
PageTables:       1392 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= 66200 MiB
End job on node9 at 2009-06-14 12:14:42