Trace number 453496

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
sat4jPseudoCPClause 2007-03-23OPT2 0.356945 0.367091

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/mds/normalized-mds_10_4_4.opb
MD5SUM31fd2df22ab91da818d86e346815effd
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.001999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables10
Total number of constraints10
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints10
Minimum length of a constraint5
Maximum length of a constraint7
Number of terms in the objective function 10
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 10
Number of bits of the sum of numbers in the objective function 4
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 10
Number of bits of the biggest sum of numbers4
Number of products (including duplicates)46
Sum of products size (including duplicates)92
Number of different products46
Sum of products size92

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.08/0.14	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.08/0.14	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.08/0.14	c This software uses some libraries from the Jakarta project. See jakarta.apache.org for details.
0.08/0.15	c no version file found!!!
0.08/0.15	c sun.arch.data.model	32
0.08/0.15	c java.version	1.6.0
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 1651659224
0.08/0.15	c Max memory 1654456320
0.08/0.15	c Total memory 1654456320
0.08/0.15	c Number of processors 2
0.20/0.21	c Cutting planes based inference (org.sat4j.minisat.constraints.pb.PBSolverClause)
0.20/0.21	--- Begin Solver configuration ---
0.20/0.21	c Stops conflict analysis at the first Unique Implication Point
0.20/0.21	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@691f36
0.20/0.21	c Learn all clauses as in MiniSAT
0.20/0.21	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=10000.0 initConflictBound=100 
0.20/0.21	c VSIDS like heuristics from MiniSAT using a heap
0.20/0.21	c No reason simplification
0.20/0.21	c --- End Solver configuration ---
0.20/0.21	c Simplify asserted PB constraints to clauses
0.20/0.21	c solving /tmp/evaluation/453496-1178140977/instance-453496-1178140977.opb
0.20/0.21	c reading problem ... 
0.20/0.24	c ... done. Wall clock time 0.035s.
0.20/0.24	c CPU time (experimental) 0.19s.
0.20/0.24	c #vars     56
0.20/0.24	c #constraints  102
0.20/0.25	c SATISFIABLE
0.20/0.25	c OPTIMIZING...
0.20/0.25	c Got one! Elapsed wall clock time (in seconds):0.043
0.20/0.25	o 3
0.32/0.32	c Got one! Elapsed wall clock time (in seconds):0.11
0.32/0.32	o 2
0.32/0.32	c starts		: 2
0.32/0.32	c conflicts		: 14
0.32/0.32	c decisions		: 25
0.32/0.32	c propagations		: 436
0.32/0.32	c inspects		: 1361
0.32/0.32	c learnt literals	: 0
0.32/0.32	c learnt binary clauses	: 0
0.32/0.32	c learnt ternary clauses	: 0
0.32/0.32	c learnt clauses	: 14
0.32/0.32	c root simplifications	: 0
0.32/0.32	c removed literals (reason simplification)	: 0
0.32/0.32	c reason swapping (by a shorter reason)	: 0
0.32/0.32	c Calls to reduceDB	: 0
0.32/0.32	c speed (decisions/second)	: 12500.0
0.32/0.32	c non guided choices	0
0.32/0.32	s OPTIMUM FOUND
0.32/0.32	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
0.32/0.32	v -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
0.32/0.32	c objective function=2
0.32/0.32	c Total wall clock time (ms): 0.114

Verifier Data (download as text)

OK	2

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node6/watcher-453496-1178140977 -o ROOT/results/node6/solver-453496-1178140977 -C 1800 -W 3600 -M 1800 --output-limit 1,15 java -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/453496-1178140977/sat4jPseudoCPClause.jar /tmp/evaluation/453496-1178140977/instance-453496-1178140977.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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.85 0.94 0.96 2/77 21632
/proc/meminfo: memFree=1829488/2055924 swapFree=4146580/4192956
[pid=21632] ppid=21630 vsize=18528 CPUtime=0
/proc/21632/stat : 21632 (runsolver) R 21630 21632 20935 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 290135332 18972672 284 18446744073709551615 4194304 4255128 548682068784 18446744073709551615 268582841639 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/21632/statm: 4632 284 249 14 0 2626 0

[startup+0.0947611 s]
/proc/loadavg: 0.85 0.94 0.96 2/77 21632
/proc/meminfo: memFree=1829488/2055924 swapFree=4146580/4192956
[pid=21632] ppid=21630 vsize=1777844 CPUtime=0.07
/proc/21632/stat : 21632 (java) S 21630 21632 20935 0 -1 0 3869 0 1 0 5 2 0 0 18 0 7 0 290135332 1820512256 3613 18446744073709551615 134512640 134550740 4294956368 18446744073709551615 4294960144 0 0 0 23755 18446744073709551615 0 0 17 1 0 0
/proc/21632/statm: 444461 3613 1096 9 0 442097 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 1777844

[startup+0.101759 s]
/proc/loadavg: 0.85 0.94 0.96 2/77 21632
/proc/meminfo: memFree=1829488/2055924 swapFree=4146580/4192956
[pid=21632] ppid=21630 vsize=1780112 CPUtime=0.08
/proc/21632/stat : 21632 (java) S 21630 21632 20935 0 -1 0 3960 0 1 0 6 2 0 0 18 0 12 0 290135332 1822834688 3703 18446744073709551615 134512640 134550740 4294956368 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/21632/statm: 445028 3703 1122 9 0 442646 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1780112

[startup+0.301785 s]
/proc/loadavg: 0.85 0.94 0.96 2/77 21632
/proc/meminfo: memFree=1829488/2055924 swapFree=4146580/4192956
[pid=21632] ppid=21630 vsize=1782760 CPUtime=0.32
/proc/21632/stat : 21632 (java) S 21630 21632 20935 0 -1 0 5154 0 1 0 29 3 0 0 18 0 13 0 290135332 1825546240 4891 18446744073709551615 134512640 134550740 4294956368 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/21632/statm: 445690 4892 1265 9 0 443301 0
Current children cumulated CPU time (s) 0.32
Current children cumulated vsize (KiB) 1782760

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

Child status: 30
Real time (s): 0.367091
CPU time (s): 0.356945
CPU user time (s): 0.317951
CPU system time (s): 0.038994
CPU usage (%): 97.2361
Max. virtual memory (cumulated for all children) (KiB): 1782760

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.317951
system time used= 0.038994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5222
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= 165
involuntary context switches= 107

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node6 on Wed May  2 21:22:57 UTC 2007

IDJOB= 453496
IDBENCH= 48134
IDSOLVER= 164
FILE ID= node6/453496-1178140977

PBS_JOBID= 4751071

Free space on /tmp= 66561 MiB

SOLVER NAME= sat4jPseudoCPClause 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/mds/normalized-mds_10_4_4.opb
COMMAND LINE= java  -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/453496-1178140977/sat4jPseudoCPClause.jar /tmp/evaluation/453496-1178140977/instance-453496-1178140977.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-453496-1178140977 -o ROOT/results/node6/solver-453496-1178140977 -C 1800 -W 3600 -M 1800 --output-limit 1,15  java  -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/453496-1178140977/sat4jPseudoCPClause.jar /tmp/evaluation/453496-1178140977/instance-453496-1178140977.opb

META MD5SUM SOLVER= 592978c395d7dcf045996aed0652cb30
MD5SUM BENCH=  31fd2df22ab91da818d86e346815effd

RANDOM SEED= 889233770

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

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

/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:      2055924 kB
MemFree:       1830088 kB
Buffers:         80688 kB
Cached:          57768 kB
SwapCached:      14272 kB
Active:          87372 kB
Inactive:        74536 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1830088 kB
SwapTotal:     4192956 kB
SwapFree:      4146580 kB
Dirty:            3764 kB
Writeback:           0 kB
Mapped:          29732 kB
Slab:            49496 kB
Committed_AS: 12373208 kB
PageTables:       1784 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= 66561 MiB

End job on node6 on Wed May  2 21:22:57 UTC 2007