Trace number 243088

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 1.7 RC BF3UNSAT 0.689894 0.582835

General information on the benchmark

Namedimacs/aim-50/
aim-50-2-0-unsat-4_ext.xml
MD5SUMf79cb268ee690a490b637d3dc655b044
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.016997
SatisfiableNO
(Un)Satisfiability was proved
Number of variables50
Number of constraints95
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension95
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
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/243088-1168383742/unknown.xml
0.22	c reading problem ... 
0.39	c reading problem named ?
0.39	c reading domains done.
0.40	c reading variables
c reading variables (50) done.
0.43	c reading relations
c reading relations (13) done.
0.44	c reading constraints
c reading constraints done.
0.51	c ... done. Wall clock time 0.292s.
0.51	c CPU time (experimental) 0.41s.
0.51	c #vars     100
0.51	c #constraints  146
0.52	c starts		: 1
0.52	c conflicts		: 16
0.52	c decisions		: 35
0.52	c propagations		: 247
0.52	c inspects		: 490
0.52	c learnt literals	: 2
0.52	c learnt binary clauses	: 0
0.52	c learnt ternary clauses	: 5
0.52	c learnt clauses	: 7
0.52	c root simplifications	: 0
0.52	c removed literals (reason simplification)	: 0
0.52	c reason swapping (by a shorter reason)	: 0
0.52	c Calls to reduceDB	: 0
0.52	c speed (decisions/second)	: 3888.888888888889
0.52	c non guided choices	22
0.52	s UNSATISFIABLE
0.52	c Total wall clock time (in seconds) : 0.303
0.52	c Total CPU time (experimental, in seconds) : 0.42

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node10/watcher-243088-1168383742 -o ROOT/results/node10/solver-243088-1168383742 -C 1800 -M 900 java -server -Xmx700M -Xms700M -jar /tmp/evaluation/243088-1168383742/sat4jCSP-bf3.jar /tmp/evaluation/243088-1168383742/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: 0.52 0.85 0.99 3/87 25223
/proc/meminfo: memFree=1826704/2055920 swapFree=4178216/4192956
[pid=25222] ppid=25220 vsize=12040 CPUtime=0
/proc/25222/stat : 25222 (java) R 25220 25222 24514 0 -1 0 395 0 0 0 0 0 0 0 18 0 1 0 186769336 12328960 202 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 8875284 0 0 4096 0 0 0 0 17 0 0 0
/proc/25222/statm: 3010 209 157 14 0 1138 0

[startup+0.108357 s]
/proc/loadavg: 0.52 0.85 0.99 3/87 25223
/proc/meminfo: memFree=1826704/2055920 swapFree=4178216/4192956
[pid=25222] ppid=25220 vsize=901540 CPUtime=0.08
/proc/25222/stat : 25222 (java) R 25220 25222 24514 0 -1 0 3358 0 1 0 6 2 0 0 23 0 12 0 186769336 923176960 3118 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/25222/statm: 225385 3118 1568 14 0 212109 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 901540

[startup+0.51642 s]
/proc/loadavg: 0.52 0.85 0.99 3/87 25223
/proc/meminfo: memFree=1826704/2055920 swapFree=4178216/4192956
[pid=25222] ppid=25220 vsize=906836 CPUtime=0.66
/proc/25222/stat : 25222 (java) R 25220 25222 24514 0 -1 0 6275 0 1 0 62 4 0 0 21 0 13 0 186769336 928600064 5817 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 4053834071 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/25222/statm: 226709 5817 2312 14 0 213146 0
Current children cumulated CPU time (s) 0.66
Current children cumulated vsize (KiB) 906836

Child status: 0
Real time (s): 0.582835
CPU time (s): 0.689894
CPU user time (s): 0.635903
CPU system time (s): 0.053991
CPU usage (%): 118.369
Max. virtual memory (cumulated for all children) (KiB): 906836

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.635903
system time used= 0.053991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6294
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= 160
involuntary context switches= 194

runsolver used 0.004999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:02:22 UTC 2007


IDJOB= 243088
IDBENCH= 7441
FILE ID= node10/243088-1168383742

PBS_JOBID= 3522534

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/aim-50/aim-50-2-0-unsat-4_ext.xml
COMMAND LINE= java -server -Xmx700M -Xms700M -jar /tmp/evaluation/243088-1168383742/sat4jCSP-bf3.jar /tmp/evaluation/243088-1168383742/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-243088-1168383742 -o ROOT/results/node10/solver-243088-1168383742 -C 1800 -M 900  java -server -Xmx700M -Xms700M -jar /tmp/evaluation/243088-1168383742/sat4jCSP-bf3.jar /tmp/evaluation/243088-1168383742/unknown.xml

META MD5SUM SOLVER= c614762dbe7de46d2af9d7b592545c03
MD5SUM BENCH=  f79cb268ee690a490b637d3dc655b044

RANDOM SEED= 860537389

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.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:       1827184 kB
Buffers:         24124 kB
Cached:         117084 kB
SwapCached:       1864 kB
Active:         116844 kB
Inactive:        59008 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1827184 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            3048 kB
Writeback:           0 kB
Mapped:          44888 kB
Slab:            37704 kB
Committed_AS:  5447692 kB
PageTables:       2292 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 node10 on Tue Jan  9 23:02:24 UTC 2007