Trace number 2683983

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-26UNSAT 0.444931 0.356183

General information on the benchmark

Name/OPT-SMALLINT-LIN/leberre/opb-trendy/misc2010/
datasets/caixa/normalized-1021.cudf.trendy.opb
MD5SUMf65d5bcc7b087f89dda1399953fc2603
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.005998
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables208
Total number of constraints930
Number of constraints which are clauses930
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint3
Number of terms in the objective function 138
Biggest coefficient in the objective function 5041
Number of bits for the biggest coefficient in the objective function 13
Sum of the numbers in the objective function 347898
Number of bits of the sum of numbers in the objective function 19
Biggest number in a constraint 5041
Number of bits of the biggest number in a constraint 13
Biggest sum of numbers in a constraint 347898
Number of bits of the biggest sum of numbers19
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.09/0.13	c SAT4J: a SATisfiability library for Java (c) 2004-2010 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.14	c version 2.2.0.v20100526
0.09/0.14	c java.runtime.name	Java(TM) SE Runtime Environment
0.09/0.14	c java.vm.name		Java HotSpot(TM) Server VM
0.09/0.14	c java.vm.version	11.2-b01
0.09/0.14	c java.vm.vendor	Sun Microsystems Inc.
0.09/0.14	c sun.arch.data.model	32
0.09/0.14	c java.version		1.6.0_12
0.09/0.14	c os.name		Linux
0.09/0.14	c os.version		2.6.18-164.el5
0.09/0.14	c os.arch		i386
0.09/0.14	c Free memory 		1393557488
0.09/0.14	c Max memory 		1395916800
0.09/0.14	c Total memory 		1395916800
0.09/0.14	c Number of processors 	2
0.09/0.20	c Pseudo Boolean Optimization
0.09/0.20	c --- Begin Solver configuration ---
0.09/0.20	c Stops conflict analysis at the first Unique Implication Point
0.09/0.20	c org.sat4j.pb.constraints.CompetResolutionPBMixedWLClauseCardConstrDataStructure@161d36b
0.09/0.20	c Learn all clauses as in MiniSAT
0.09/0.20	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.09/0.20	c VSIDS like heuristics from MiniSAT using a heap lightweight component caching from RSAT taking into account the objective function
0.09/0.20	c Expensive reason simplification
0.09/0.20	c Armin Biere (Picosat) restarts strategy
0.09/0.20	c Glucose learned constraints deletion strategy
0.09/0.20	c timeout=2147483s
0.09/0.20	c DB Simplification allowed=false
0.09/0.20	c --- End Solver configuration ---
0.09/0.20	c solving HOME/instance-2683983-1277511696.opb
0.09/0.20	c reading problem ... 
0.36/0.33	c (trivial inconsistency)
0.36/0.33	c starts		: 0
0.36/0.33	c conflicts		: 0
0.36/0.33	c decisions		: 0
0.36/0.33	c propagations		: 0
0.36/0.33	c inspects		: 0
0.36/0.33	c learnt literals	: 0
0.36/0.33	c learnt binary clauses	: 0
0.36/0.33	c learnt ternary clauses	: 0
0.36/0.33	c learnt clauses	: 0
0.36/0.33	c ignored clauses	: 0
0.36/0.33	c root simplifications	: 0
0.36/0.34	c removed literals (reason simplification)	: 0
0.36/0.34	c reason swapping (by a shorter reason)	: 0
0.36/0.34	c Calls to reduceDB	: 0
0.36/0.34	c number of reductions to clauses (during analyze)	: 0
0.36/0.34	c number of learned constraints concerned by reduction	: 0
0.36/0.34	c number of learning phase by resolution	: 0
0.36/0.34	c number of learning phase by cutting planes	: 0
0.36/0.34	c speed (assignments/second)	: 0.0
0.36/0.34	c non guided choices	0
0.36/0.34	c learnt constraints type 
0.36/0.34	c constraints type 
0.36/0.34	c org.sat4j.minisat.constraints.cnf.OriginalWLClause => 76
0.36/0.34	c org.sat4j.minisat.constraints.cnf.OriginalBinaryClause => 574
0.36/0.34	s UNSATISFIABLE
0.36/0.34	c Total wall clock time (in seconds): 0.139

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2683983-1277511696/watcher-2683983-1277511696 -o /tmp/evaluation-result-2683983-1277511696/solver-2683983-1277511696 -C 1800 -W 2000 -M 1800 java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar HOME/instance-2683983-1277511696.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.96 0.97 3/106 30217
/proc/meminfo: memFree=1855816/2059040 swapFree=4135148/4192956
[pid=30217] ppid=30215 vsize=13164 CPUtime=0
/proc/30217/stat : 30217 (java) R 30215 30217 27940 0 -1 4194304 619 0 0 0 0 0 0 0 19 0 1 0 126771186 13479936 266 1992294400 134512640 134550932 4287161824 18446744073709551615 6342267 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/30217/statm: 3291 271 141 10 0 1121 0

[startup+0.056339 s]
/proc/loadavg: 0.92 0.96 0.97 3/106 30217
/proc/meminfo: memFree=1855816/2059040 swapFree=4135148/4192956
[pid=30217] ppid=30215 vsize=1521664 CPUtime=0.04
/proc/30217/stat : 30217 (java) S 30215 30217 27940 0 -1 4202496 3620 0 1 0 3 1 0 0 19 0 7 0 126771186 1558183936 3061 1992294400 134512640 134550932 4287161824 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 1 0 0 0
/proc/30217/statm: 380416 3061 1023 10 0 377726 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 1521664

[startup+0.101349 s]
/proc/loadavg: 0.92 0.96 0.97 3/106 30217
/proc/meminfo: memFree=1855816/2059040 swapFree=4135148/4192956
[pid=30217] ppid=30215 vsize=1524184 CPUtime=0.09
/proc/30217/stat : 30217 (java) S 30215 30217 27940 0 -1 4202496 3999 0 1 0 7 2 0 0 19 0 12 0 126771186 1560764416 3438 1992294400 134512640 134550932 4287161824 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0 0
/proc/30217/statm: 381046 3438 1078 10 0 378348 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1524184

[startup+0.300175 s]
/proc/loadavg: 0.92 0.96 0.97 3/106 30217
/proc/meminfo: memFree=1855816/2059040 swapFree=4135148/4192956
[pid=30217] ppid=30215 vsize=1526664 CPUtime=0.36
/proc/30217/stat : 30217 (java) S 30215 30217 27940 0 -1 4202496 5429 0 1 0 33 3 0 0 19 0 12 0 126771186 1563303936 4866 1992294400 134512640 134550932 4287161824 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0 0
/proc/30217/statm: 381666 4866 1361 10 0 378968 0
Current children cumulated CPU time (s) 0.36
Current children cumulated vsize (KiB) 1526664

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

Child status: 20
Real time (s): 0.356183
CPU time (s): 0.444931
CPU user time (s): 0.410937
CPU system time (s): 0.033994
CPU usage (%): 124.916
Max. virtual memory (cumulated for all children) (KiB): 1526664

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.410937
system time used= 0.033994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5555
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= 82
involuntary context switches= 43

runsolver used 0.004999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node011 at 2010-06-26 02:21:36
IDJOB=2683983
IDBENCH=72154
IDSOLVER=1164
FILE ID=node011/2683983-1277511696
PBS_JOBID= 11190638
Free space on /tmp= 62404 MiB

SOLVER NAME= SAT4J PB Resolution 2.2.0 2010-05-26
BENCH NAME= PB10/normalized-PB10/OPT-SMALLINT-LIN/leberre/opb-trendy/misc2010/datasets/caixa/normalized-1021.cudf.trendy.opb
COMMAND LINE= java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2683983-1277511696/watcher-2683983-1277511696 -o /tmp/evaluation-result-2683983-1277511696/solver-2683983-1277511696 -C 1800 -W 2000 -M 1800  java6 -server -Xmx1350m -Xms1350m -jar HOME/sat4j-pb.jar HOME/instance-2683983-1277511696.opb

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

MD5SUM BENCH= f65d5bcc7b087f89dda1399953fc2603
RANDOM SEED=872541016

node011.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.264
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.52
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.264
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.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1856212 kB
Buffers:          8508 kB
Cached:         105508 kB
SwapCached:      10048 kB
Active:         105668 kB
Inactive:        21140 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1856212 kB
SwapTotal:     4192956 kB
SwapFree:      4135148 kB
Dirty:            1128 kB
Writeback:           0 kB
AnonPages:       11560 kB
Mapped:           8360 kB
Slab:            54040 kB
PageTables:       4160 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182400 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= 62404 MiB
End job on node011 at 2010-06-26 02:21:37