Trace number 242905

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 NameAnswerCPU timeWall clock time
SAT4JCSP-CACHED 1.7 RC BF3SAT 0.793878 0.634805

General information on the benchmark

Namedimacs/aim-50/
aim-50-3-4-sat-4_ext.xml
MD5SUMcd09149f62c1745a4886e8b13a2f80cb
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.019996
SatisfiableYES
(Un)Satisfiability was proved
Number of variables50
Number of constraints159
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension159
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.15	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.15	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.15	c This software uses some libraries from the Jakarta project. See jakarta.apache.org for details.
0.16	c version CSP COMPETITION BUGFIX 3 CACHED
0.16	c sun.arch.data.model	32
0.16	c java.version	1.5.0_10
0.16	c os.name	Linux
0.16	c os.version	2.6.9-22.EL.rootsmp
0.16	c os.arch	i386
0.16	c Free memory 722620888
0.16	c Max memory 723845120
0.16	c Total memory 723845120
0.16	c Number of processors 2
0.22	c --- Begin Solver configuration ---
0.22	c Stops conflict analysis at the first Unique Implication Point
0.22	c org.sat4j.minisat.constraints.MixedDataStructureWithBinary@19dfbff
0.22	c Learn all clauses as in MiniSAT
0.22	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.22	c VSIDS like heuristics from MiniSAT using a heap
0.22	c No reason simplification
0.22	c --- End Solver configuration ---
0.22	c solving /tmp/evaluation/242905-1168382943/unknown.xml
0.22	c reading problem ... 
0.39	c reading problem named ?
0.39	c reading domains done.
0.39	c reading variables
c reading variables (50) done.
0.42	c reading relations
c reading relations (17) done.
0.43	c reading constraints
c reading constraints done.
0.55	c ... done. Wall clock time 0.33s.
0.55	c CPU time (experimental) 0.44s.
0.55	c #vars     100
0.55	c #constraints  218
0.57	c starts		: 1
0.57	c conflicts		: 35
0.57	c decisions		: 53
0.57	c propagations		: 878
0.57	c inspects		: 2319
0.57	c learnt literals	: 1
0.57	c learnt binary clauses	: 0
0.57	c learnt ternary clauses	: 6
0.58	c learnt clauses	: 24
0.58	c root simplifications	: 0
0.58	c removed literals (reason simplification)	: 0
0.58	c reason swapping (by a shorter reason)	: 0
0.58	c Calls to reduceDB	: 0
0.58	c speed (decisions/second)	: 2304.3478260869565
0.58	c non guided choices	6
0.58	s SATISFIABLE
0.58	v 0 0 1 1 1 1 0 0 1 1 0 0 0 1 1 0 1 0 1 0 0 0 1 0 1 0 0 1 0 1 0 1 1 1 0 1 0 0 1 0 0 0 1 0 0 0 0 1 0 1 
0.58	c Total wall clock time (in seconds) : 0.355
0.58	c Total CPU time (experimental, in seconds) : 0.46

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node9/watcher-242905-1168382943 -o ROOT/results/node9/solver-242905-1168382943 -C 1800 -M 900 java -server -Xmx700M -Xms700M -jar /tmp/evaluation/242905-1168382943/sat4jCSP-bf3-cached.jar /tmp/evaluation/242905-1168382943/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.04 1.72 1.78 3/81 29660
/proc/meminfo: memFree=1745504/2055920 swapFree=4191880/4192956
[pid=29659] ppid=29657 vsize=172 CPUtime=0
/proc/29659/stat : 29659 (java) R 29657 29659 29034 0 -1 0 201 0 0 0 0 0 0 0 18 0 1 0 186689587 176128 24 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 8663339 0 0 4096 0 0 0 0 17 1 0 0
/proc/29659/statm: 43 24 18 14 0 3 0

[startup+0.103423 s]
/proc/loadavg: 1.04 1.72 1.78 3/81 29660
/proc/meminfo: memFree=1745504/2055920 swapFree=4191880/4192956
[pid=29659] ppid=29657 vsize=901540 CPUtime=0.09
/proc/29659/stat : 29659 (java) R 29657 29659 29034 0 -1 0 3359 0 1 0 7 2 0 0 23 0 12 0 186689587 923176960 3119 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4160643169 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/29659/statm: 225385 3119 1570 14 0 212109 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 901540

[startup+0.515467 s]
/proc/loadavg: 1.04 1.72 1.78 3/81 29660
/proc/meminfo: memFree=1745504/2055920 swapFree=4191880/4192956
[pid=29659] ppid=29657 vsize=906224 CPUtime=0.69
/proc/29659/stat : 29659 (java) R 29657 29659 29034 0 -1 0 6280 0 1 0 65 4 0 0 18 0 12 0 186689587 927973376 5855 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4053846338 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/29659/statm: 226556 5855 2306 14 0 212993 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 906224

Child status: 0
Real time (s): 0.634805
CPU time (s): 0.793878
CPU user time (s): 0.746886
CPU system time (s): 0.046992
CPU usage (%): 125.059
Max. virtual memory (cumulated for all children) (KiB): 906740

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.746886
system time used= 0.046992
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6375
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= 164
involuntary context switches= 163

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Tue Jan  9 22:49:04 UTC 2007


IDJOB= 242905
IDBENCH= 7427
FILE ID= node9/242905-1168382943

PBS_JOBID= 3522452

Free space on /tmp= 66544 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/aim-50/aim-50-3-4-sat-4_ext.xml
COMMAND LINE= java -server -Xmx700M -Xms700M -jar /tmp/evaluation/242905-1168382943/sat4jCSP-bf3-cached.jar /tmp/evaluation/242905-1168382943/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-242905-1168382943 -o ROOT/results/node9/solver-242905-1168382943 -C 1800 -M 900  java -server -Xmx700M -Xms700M -jar /tmp/evaluation/242905-1168382943/sat4jCSP-bf3-cached.jar /tmp/evaluation/242905-1168382943/unknown.xml

META MD5SUM SOLVER= c614762dbe7de46d2af9d7b592545c03
MD5SUM BENCH=  cd09149f62c1745a4886e8b13a2f80cb

RANDOM SEED= 762348604

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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:       1745920 kB
Buffers:         49400 kB
Cached:         167180 kB
SwapCached:        408 kB
Active:         173200 kB
Inactive:        90500 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1745920 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            5560 kB
Writeback:           0 kB
Mapped:          58724 kB
Slab:            31396 kB
Committed_AS:  6187012 kB
PageTables:       2136 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= 66544 MiB



End job on node9 on Tue Jan  9 22:49:05 UTC 2007