Trace number 244406

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 BF3UNSAT 1.9547 1.21544

General information on the benchmark

Namedimacs/jnhUnsat/
jnh19_ext.xml
MD5SUMd97c1d738f3faf99952d530923f0723b
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.076987
SatisfiableNO
(Un)Satisfiability was proved
Number of variables100
Number of constraints850
Maximum constraint arity11
Maximum domain size2
Number of constraints which are defined in extension850
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.14	c SAT4J: a SATisfiability library for Java (c) 2004-2006 Daniel Le Berre
0.14	c This is free software under the GNU LGPL licence. See www.sat4j.org for details.
0.14	c This software uses some libraries from the Jakarta project. See jakarta.apache.org for details.
0.14	c version CSP COMPETITION BUGFIX 3 CACHED
0.14	c sun.arch.data.model	32
0.14	c java.version	1.5.0_10
0.14	c os.name	Linux
0.14	c os.version	2.6.9-22.EL.rootsmp
0.14	c os.arch	i386
0.14	c Free memory 722620888
0.14	c Max memory 723845120
0.14	c Total memory 723845120
0.15	c Number of processors 2
0.20	c --- Begin Solver configuration ---
0.20	c Stops conflict analysis at the first Unique Implication Point
0.20	c org.sat4j.minisat.constraints.MixedDataStructureWithBinary@19dfbff
0.20	c Learn all clauses as in MiniSAT
0.20	c claDecay=0.999 varDecay=0.95 conflictBoundIncFactor=1.5 initConflictBound=100 
0.20	c VSIDS like heuristics from MiniSAT using a heap
0.20	c No reason simplification
0.20	c --- End Solver configuration ---
0.20	c solving /tmp/evaluation/244406-1168385769/unknown.xml
0.20	c reading problem ... 
0.37	c reading problem named ?
0.37	c reading domains done.
0.38	c reading variables
c reading variables (100) done.
0.42	c reading relations
c reading relations (226) done.
0.58	c reading constraints
c reading constraints done.
1.02	c ... done. Wall clock time 0.812s.
1.02	c CPU time (experimental) 0.89s.
1.02	c #vars     200
1.02	c #constraints  889
1.10	c starts		: 1
1.10	c conflicts		: 25
1.10	c decisions		: 28
1.10	c propagations		: 1467
1.10	c inspects		: 5952
1.10	c learnt literals	: 1
1.10	c learnt binary clauses	: 0
1.10	c learnt ternary clauses	: 4
1.10	c learnt clauses	: 20
1.10	c root simplifications	: 0
1.10	c removed literals (reason simplification)	: 0
1.10	c reason swapping (by a shorter reason)	: 0
1.10	c Calls to reduceDB	: 0
1.10	c speed (decisions/second)	: 337.34939759036143
1.10	c non guided choices	8
1.10	s UNSATISFIABLE
1.10	c Total wall clock time (in seconds) : 0.897
1.10	c Total CPU time (experimental, in seconds) : 0.93

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-244406-1168385769 -o ROOT/results/node10/solver-244406-1168385769 -C 1800 -M 900 java -server -Xmx700M -Xms700M -jar /tmp/evaluation/244406-1168385769/sat4jCSP-bf3-cached.jar /tmp/evaluation/244406-1168385769/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.76 0.94 0.90 4/81 29046
/proc/meminfo: memFree=1824824/2055920 swapFree=4178216/4192956
[pid=29045] ppid=29043 vsize=172 CPUtime=0
/proc/29045/stat : 29045 (java) R 29043 29045 28567 0 -1 0 201 0 0 0 0 0 0 0 18 0 1 0 186972316 176128 24 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 8905003 0 0 4096 0 0 0 0 17 1 0 0
/proc/29045/statm: 43 24 18 14 0 3 0

[startup+0.103544 s]
/proc/loadavg: 0.76 0.94 0.90 4/81 29046
/proc/meminfo: memFree=1824824/2055920 swapFree=4178216/4192956
[pid=29045] ppid=29043 vsize=902816 CPUtime=0.09
/proc/29045/stat : 29045 (java) R 29043 29045 28567 0 -1 0 3418 0 1 0 8 1 0 0 24 0 12 0 186972316 924483584 3178 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 4155225878 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/29045/statm: 225704 3178 1586 14 0 212148 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 902816

[startup+0.5116 s]
/proc/loadavg: 0.76 0.94 0.90 4/81 29046
/proc/meminfo: memFree=1824824/2055920 swapFree=4178216/4192956
[pid=29045] ppid=29043 vsize=906436 CPUtime=0.69
/proc/29045/stat : 29045 (java) R 29043 29045 28567 0 -1 0 6315 0 1 0 66 3 0 0 19 0 12 0 186972316 928190464 5866 18446744073709551615 134512640 134570532 4294956496 18446744073709551615 4151513458 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/29045/statm: 226609 5866 2308 14 0 213046 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 906436

Child status: 0
Real time (s): 1.21544
CPU time (s): 1.9547
CPU user time (s): 1.90071
CPU system time (s): 0.053991
CPU usage (%): 160.822
Max. virtual memory (cumulated for all children) (KiB): 907580

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.90071
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= 7872
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= 276
involuntary context switches= 266

runsolver used 0.003999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:36:10 UTC 2007


IDJOB= 244406
IDBENCH= 8476
FILE ID= node10/244406-1168385769

PBS_JOBID= 3522614

Free space on /tmp= 66561 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/jnhUnsat/jnh19_ext.xml
COMMAND LINE= java -server -Xmx700M -Xms700M -jar /tmp/evaluation/244406-1168385769/sat4jCSP-bf3-cached.jar /tmp/evaluation/244406-1168385769/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-244406-1168385769 -o ROOT/results/node10/solver-244406-1168385769 -C 1800 -M 900  java -server -Xmx700M -Xms700M -jar /tmp/evaluation/244406-1168385769/sat4jCSP-bf3-cached.jar /tmp/evaluation/244406-1168385769/unknown.xml

META MD5SUM SOLVER= c614762dbe7de46d2af9d7b592545c03
MD5SUM BENCH=  d97c1d738f3faf99952d530923f0723b

RANDOM SEED= 379783330

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:       1825176 kB
Buffers:         26436 kB
Cached:         118240 kB
SwapCached:       1864 kB
Active:         122996 kB
Inactive:        55592 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1825176 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            3040 kB
Writeback:           0 kB
Mapped:          43688 kB
Slab:            37276 kB
Committed_AS:  5535488 kB
PageTables:       2064 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:36:13 UTC 2007