Trace number 431305

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-23OPT3 0.411937 0.365081

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=17-P1=5-B.opb
MD5SUM8ed99f7308112b5bc8fe8bbf0181abb7
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
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 3
Optimality of the best value was proved YES
Number of variables15
Total number of constraints3
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 constraints3
Minimum length of a constraint5
Maximum length of a constraint30
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 1974
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)25
Sum of products size (including duplicates)50
Number of different products25
Sum of products size50

Solver Data (download as text)

0.09/0.13	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.09/0.13	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.09/0.13	c This software uses some libraries from the Jakarta project. See jakarta.apache.org for details.
0.09/0.14	c no version file found!!!
0.09/0.14	c sun.arch.data.model	32
0.09/0.14	c java.version	1.6.0
0.09/0.14	c os.name	Linux
0.09/0.14	c os.version	2.6.9-22.EL.rootsmp
0.09/0.14	c os.arch	i386
0.09/0.14	c Free memory 1651659224
0.09/0.14	c Max memory 1654456320
0.09/0.14	c Total memory 1654456320
0.09/0.14	c Number of processors 2
0.20/0.20	c Cutting planes based inference (org.sat4j.minisat.constraints.pb.PBSolverClause)
0.20/0.20	--- Begin Solver configuration ---
0.20/0.20	c Stops conflict analysis at the first Unique Implication Point
0.20/0.20	c org.sat4j.minisat.constraints.PBMaxClauseCardConstrDataStructure@691f36
0.20/0.20	c Learn all clauses as in MiniSAT
0.20/0.20	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=10000.0 initConflictBound=100 
0.20/0.20	c VSIDS like heuristics from MiniSAT using a heap
0.20/0.20	c No reason simplification
0.20/0.20	c --- End Solver configuration ---
0.20/0.20	c Simplify asserted PB constraints to clauses
0.20/0.20	c solving /tmp/evaluation/431305-1178004561/instance-431305-1178004561.opb
0.20/0.20	c reading problem ... 
0.20/0.23	c ... done. Wall clock time 0.027s.
0.20/0.23	c CPU time (experimental) 0.19s.
0.20/0.23	c #vars     40
0.20/0.23	c #constraints  54
0.20/0.30	c SATISFIABLE
0.20/0.30	c OPTIMIZING...
0.20/0.30	c Got one! Elapsed wall clock time (in seconds):0.097
0.20/0.30	o 3
0.34/0.34	c starts		: 2
0.34/0.34	c conflicts		: 13
0.34/0.34	c decisions		: 16
0.34/0.34	c propagations		: 137
0.34/0.34	c inspects		: 355
0.34/0.34	c learnt literals	: 0
0.34/0.34	c learnt binary clauses	: 0
0.34/0.34	c learnt ternary clauses	: 0
0.34/0.34	c learnt clauses	: 12
0.34/0.34	c root simplifications	: 0
0.34/0.34	c removed literals (reason simplification)	: 0
0.34/0.34	c reason swapping (by a shorter reason)	: 0
0.34/0.34	c Calls to reduceDB	: 0
0.34/0.34	c speed (decisions/second)	: 400.0
0.34/0.34	c non guided choices	2
0.34/0.34	s OPTIMUM FOUND
0.34/0.34	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.34/0.34	v -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40
0.34/0.34	c objective function=3
0.34/0.34	c Total wall clock time (ms): 0.137

Verifier Data (download as text)

OK	3

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node41/watcher-431305-1178004561 -o ROOT/results/node41/solver-431305-1178004561 -C 1800 -W 3600 -M 1800 --output-limit 1,15 java -server -Xms1600M -Xmx1600M -jar /tmp/evaluation/431305-1178004561/sat4jPseudoCPClause.jar /tmp/evaluation/431305-1178004561/instance-431305-1178004561.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: 1.07 1.01 1.00 2/77 31317
/proc/meminfo: memFree=1831128/2055920 swapFree=4169228/4192956
[pid=31317] ppid=31315 vsize=1800 CPUtime=0
/proc/31317/stat : 31317 (java) R 31315 31317 27720 0 -1 0 169 0 0 0 0 0 0 0 19 0 1 0 248368067 1843200 143 18446744073709551615 134512640 134550740 4294956592 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/31317/statm: 450 143 106 9 0 92 0

[startup+0.0989849 s]
/proc/loadavg: 1.07 1.01 1.00 2/77 31317
/proc/meminfo: memFree=1831128/2055920 swapFree=4169228/4192956
[pid=31317] ppid=31315 vsize=1780112 CPUtime=0.09
/proc/31317/stat : 31317 (java) S 31315 31317 27720 0 -1 0 3982 0 1 0 6 3 0 0 18 0 12 0 248368067 1822834688 3725 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/31317/statm: 445028 3725 1123 9 0 442646 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1780112

[startup+0.101981 s]
/proc/loadavg: 1.07 1.01 1.00 2/77 31317
/proc/meminfo: memFree=1831128/2055920 swapFree=4169228/4192956
[pid=31317] ppid=31315 vsize=1780260 CPUtime=0.09
/proc/31317/stat : 31317 (java) S 31315 31317 27720 0 -1 0 4010 0 1 0 6 3 0 0 18 0 12 0 248368067 1822986240 3753 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/31317/statm: 445065 3753 1124 9 0 442683 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1780260

[startup+0.302003 s]
/proc/loadavg: 1.07 1.01 1.00 2/77 31317
/proc/meminfo: memFree=1831128/2055920 swapFree=4169228/4192956
[pid=31317] ppid=31315 vsize=1781736 CPUtime=0.34
/proc/31317/stat : 31317 (java) S 31315 31317 27720 0 -1 0 5190 0 1 0 30 4 0 0 18 0 13 0 248368067 1824497664 4927 18446744073709551615 134512640 134550740 4294956448 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/31317/statm: 445434 4928 1278 9 0 443045 0
Current children cumulated CPU time (s) 0.34
Current children cumulated vsize (KiB) 1781736

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

Child status: 30
Real time (s): 0.365081
CPU time (s): 0.411937
CPU user time (s): 0.365944
CPU system time (s): 0.045993
CPU usage (%): 112.834
Max. virtual memory (cumulated for all children) (KiB): 1781736

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.365944
system time used= 0.045993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5311
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= 140
involuntary context switches= 110

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node41 on Tue May  1 07:29:21 UTC 2007

IDJOB= 431305
IDBENCH= 48042
IDSOLVER= 164
FILE ID= node41/431305-1178004561

PBS_JOBID= 4728225

Free space on /tmp= 66561 MiB

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

META MD5SUM SOLVER= 592978c395d7dcf045996aed0652cb30
MD5SUM BENCH=  8ed99f7308112b5bc8fe8bbf0181abb7

RANDOM SEED= 765021725

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node41.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:      2055920 kB
MemFree:       1831536 kB
Buffers:         29856 kB
Cached:         106048 kB
SwapCached:       2476 kB
Active:          72732 kB
Inactive:        86940 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1831536 kB
SwapTotal:     4192956 kB
SwapFree:      4169228 kB
Dirty:            3772 kB
Writeback:           0 kB
Mapped:          31292 kB
Slab:            50048 kB
Committed_AS:  3661332 kB
PageTables:       2012 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 node41 on Tue May  1 07:29:22 UTC 2007