Trace number 430264

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
SAT4JPseudoResolution 2007-03-23OPT2 0.283956 0.366728

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
roussel/factor-mod-B/factor-mod-size=5-P0=11-P1=2-P2=23-B.opb
MD5SUMed9e9f2605ba126b1c81d5ad0f7f804b
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.006998
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 variables30
Total number of constraints5
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 constraints5
Minimum length of a constraint5
Maximum length of a constraint35
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 512
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 1984
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)50
Sum of products size (including duplicates)100
Number of different products50
Sum of products size100

Solver Data (download as text)

0.06/0.19	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.06/0.19	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.06/0.19	c This software uses some libraries from the Jakarta project. See jakarta.apache.org for details.
0.13/0.20	c no version file found!!!
0.13/0.20	c sun.arch.data.model	32
0.13/0.20	c java.version	1.6.0
0.13/0.20	c os.name	Linux
0.13/0.20	c os.version	2.6.9-22.EL.rootsmp
0.13/0.20	c os.arch	i386
0.13/0.20	c Free memory 1651659224
0.13/0.20	c Max memory 1654456320
0.13/0.20	c Total memory 1654456320
0.13/0.20	c Number of processors 2
0.13/0.26	--- Begin Solver configuration ---
0.13/0.26	c Stops conflict analysis at the first Unique Implication Point
0.13/0.26	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@691f36
0.13/0.26	c Learn all clauses as in MiniSAT
0.13/0.26	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.13/0.26	c VSIDS like heuristics from MiniSAT using a heap
0.13/0.26	c No reason simplification
0.13/0.26	c --- End Solver configuration ---
0.13/0.26	c solving /tmp/evaluation/430264-1177993489/instance-430264-1177993489.opb
0.13/0.26	c reading problem ... 
0.24/0.30	c ... done. Wall clock time 0.04s.
0.24/0.30	c CPU time (experimental) 0.2s.
0.24/0.30	c #vars     80
0.24/0.30	c #constraints  107
0.24/0.32	c SATISFIABLE
0.24/0.32	c OPTIMIZING...
0.24/0.32	c Got one! Elapsed wall clock time (in seconds):0.062
0.24/0.32	o 2
0.24/0.32	c starts		: 1
0.24/0.32	c conflicts		: 16
0.24/0.32	c decisions		: 43
0.24/0.32	c propagations		: 254
0.24/0.32	c inspects		: 784
0.24/0.32	c learnt literals	: 0
0.24/0.32	c learnt binary clauses	: 0
0.24/0.32	c learnt ternary clauses	: 0
0.24/0.32	c learnt clauses	: 16
0.24/0.32	c root simplifications	: 0
0.24/0.32	c removed literals (reason simplification)	: 0
0.24/0.32	c reason swapping (by a shorter reason)	: 0
0.24/0.32	c Calls to reduceDB	: 0
0.24/0.32	c speed (decisions/second)	: 21500.0
0.24/0.32	c non guided choices	24
0.24/0.32	s OPTIMUM FOUND
0.24/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 -x30 -x31
0.24/0.32	v 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.24/0.32	v x59 x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 x77 -x78 x79 x80
0.24/0.32	c objective function=2
0.24/0.32	c Total wall clock time (ms): 0.066

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/node33/watcher-430264-1177993489 -o ROOT/results/node33/solver-430264-1177993489 -C 1800 -W 3600 -M 1800 --output-limit 1,15 java -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/430264-1177993489/sat4jPseudoResolution.jar /tmp/evaluation/430264-1177993489/instance-430264-1177993489.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.91 0.95 0.98 2/77 28840
/proc/meminfo: memFree=1830824/2055920 swapFree=4147808/4192956
[pid=28840] ppid=28838 vsize=1800 CPUtime=0
/proc/28840/stat : 28840 (java) D 28838 28840 28595 0 -1 0 169 0 0 0 0 0 0 0 18 0 1 0 247264403 1843200 143 18446744073709551615 134512640 134550740 4294956592 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/28840/statm: 450 143 106 9 0 92 0

[startup+0.0272431 s]
/proc/loadavg: 0.91 0.95 0.98 2/77 28840
/proc/meminfo: memFree=1830824/2055920 swapFree=4147808/4192956
[pid=28840] ppid=28838 vsize=1774248 CPUtime=0.01
/proc/28840/stat : 28840 (java) S 28838 28840 28595 0 -1 0 2653 0 1 0 0 1 0 0 18 0 4 0 247264403 1816829952 2403 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 7368 18446744073709551615 0 0 17 1 0 0
/proc/28840/statm: 443562 2405 466 9 0 441576 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 1774248

[startup+0.101251 s]
/proc/loadavg: 0.91 0.95 0.98 2/77 28840
/proc/meminfo: memFree=1830824/2055920 swapFree=4147808/4192956
[pid=28840] ppid=28838 vsize=1777844 CPUtime=0.06
/proc/28840/stat : 28840 (java) S 28838 28840 28595 0 -1 0 3808 0 1 0 4 2 0 0 18 0 7 0 247264403 1820512256 3552 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 23755 18446744073709551615 0 0 17 1 0 0
/proc/28840/statm: 444461 3552 1089 9 0 442097 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 1777844

[startup+0.301297 s]
/proc/loadavg: 0.91 0.95 0.98 2/77 28840
/proc/meminfo: memFree=1830824/2055920 swapFree=4147808/4192956
[pid=28840] ppid=28838 vsize=1782332 CPUtime=0.24
/proc/28840/stat : 28840 (java) S 28838 28840 28595 0 -1 0 4989 0 1 0 21 3 0 0 18 0 12 0 247264403 1825107968 4729 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/28840/statm: 445583 4731 1249 9 0 443195 0
Current children cumulated CPU time (s) 0.24
Current children cumulated vsize (KiB) 1782332

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

Child status: 30
Real time (s): 0.366728
CPU time (s): 0.283956
CPU user time (s): 0.239963
CPU system time (s): 0.043993
CPU usage (%): 77.4296
Max. virtual memory (cumulated for all children) (KiB): 1782332

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.239963
system time used= 0.043993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5060
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= 106
involuntary context switches= 53

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node33 on Tue May  1 04:24:49 UTC 2007

IDJOB= 430264
IDBENCH= 47968
IDSOLVER= 159
FILE ID= node33/430264-1177993489

PBS_JOBID= 4728246

Free space on /tmp= 66561 MiB

SOLVER NAME= SAT4JPseudoResolution 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=5-P0=11-P1=2-P2=23-B.opb
COMMAND LINE= java -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/430264-1177993489/sat4jPseudoResolution.jar /tmp/evaluation/430264-1177993489/instance-430264-1177993489.opb           
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node33/watcher-430264-1177993489 -o ROOT/results/node33/solver-430264-1177993489 -C 1800 -W 3600 -M 1800 --output-limit 1,15  java -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/430264-1177993489/sat4jPseudoResolution.jar /tmp/evaluation/430264-1177993489/instance-430264-1177993489.opb           

META MD5SUM SOLVER= 592978c395d7dcf045996aed0652cb30
MD5SUM BENCH=  ed9e9f2605ba126b1c81d5ad0f7f804b

RANDOM SEED= 640312355

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node33.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.272
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.272
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:       1831232 kB
Buffers:         41328 kB
Cached:          97228 kB
SwapCached:      13560 kB
Active:          85204 kB
Inactive:        76416 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1831232 kB
SwapTotal:     4192956 kB
SwapFree:      4147808 kB
Dirty:            3792 kB
Writeback:           0 kB
Mapped:          29624 kB
Slab:            48336 kB
Committed_AS:  2602884 kB
PageTables:       1992 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 node33 on Tue May  1 04:24:50 UTC 2007