Trace number 278784

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
CSP4J - MaxCSP 2006-12-19SAT 0.406937 0.446773

DiagnosticValue
NODES4

General information on the benchmark

NameMaxCSP/kbtree/kbtree-9-7-3-5/kbtree-9-7-3-5-10/
kbtree-9-7-3-5-10-21_ext.xml
MD5SUM4bd19d83ae616f3d7b9a2b3141b34394
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints189
Best CPU time to get the best result obtained on this benchmark0.05499
SatisfiableYES
(Un)Satisfiability was proved
Number of variables28
Number of constraints189
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension189
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.42	s SATISFIABLE
0.42	o 186
0.42	v 1 1 0 1 2 3 2 0 3 0 1 0 3 0 2 2 0 0 1 0 3 0 3 0 3 1 2 3 
0.42	o 187
0.42	v 1 1 1 1 2 3 2 0 3 0 1 0 3 0 2 2 0 0 1 0 3 0 3 4 3 1 2 3 
0.42	o 188
0.42	v 1 3 1 1 2 3 2 0 3 0 1 0 3 0 2 2 0 0 1 0 3 0 3 4 3 1 2 3 
0.42	o 189
0.42	v 1 3 1 1 2 3 2 0 3 0 4 0 3 0 2 2 0 0 1 0 3 0 3 4 3 1 2 3 
0.42	s OPTIMUM FOUND
0.42	d NODES 4

Verifier Data (download as text)

0 unsatisfied constraints, 189 satisfied constraints

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-278784-1169289252 -o ROOT/results/node2/solver-278784-1169289252 -C 2400 -M 900 /tmp/evaluation/278784-1169289252/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278784-1169289252/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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.70 1.14 1.53 5/94 23762
/proc/meminfo: memFree=1214488/2055920 swapFree=4180552/4192956
[pid=23760] ppid=23758 vsize=5352 CPUtime=0
/proc/23760/stat : 23760 (cspfj.sh) S 23758 23760 23680 0 -1 4194304 315 128 0 0 0 0 0 0 17 0 1 0 277321271 5480448 240 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 206381310788 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/23760/statm: 1338 240 201 169 0 49 0
[pid=23763] ppid=23760 vsize=1788 CPUtime=0
/proc/23763/stat : 23763 (java) R 23760 23760 23680 0 -1 0 193 0 0 0 0 0 0 0 18 0 1 0 277321271 1830912 160 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/23763/statm: 447 159 123 14 0 92 0

[startup+0.106622 s]
/proc/loadavg: 0.70 1.14 1.53 5/94 23762
/proc/meminfo: memFree=1214488/2055920 swapFree=4180552/4192956
[pid=23760] ppid=23758 vsize=5352 CPUtime=0
/proc/23760/stat : 23760 (cspfj.sh) S 23758 23760 23680 0 -1 4194304 315 128 0 0 0 0 0 0 17 0 1 0 277321271 5480448 240 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 206381310788 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/23760/statm: 1338 240 201 169 0 49 0
[pid=23763] ppid=23760 vsize=864484 CPUtime=0.08
/proc/23763/stat : 23763 (java) R 23760 23760 23680 0 -1 0 2623 0 1 0 7 1 0 0 21 0 8 0 277321271 885231616 2367 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155171597 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/23763/statm: 216121 2367 1406 14 0 203419 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 869836

Child status: 0
Real time (s): 0.446773
CPU time (s): 0.406937
CPU user time (s): 0.370943
CPU system time (s): 0.035994
CPU usage (%): 91.0836
Max. virtual memory (cumulated for all children) (KiB): 870352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.370943
system time used= 0.035994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4186
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= 490
involuntary context switches= 446

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Sat Jan 20 10:34:13 UTC 2007


IDJOB= 278784
IDBENCH= 8853
IDSOLVER= 65
FILE ID= node2/278784-1169289252

PBS_JOBID= 3609565

Free space on /tmp= 66563 MiB

SOLVER NAME= CSP4J - MaxCSP 2006-12-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-9-7-3-5/kbtree-9-7-3-5-10/kbtree-9-7-3-5-10-21_ext.xml
COMMAND LINE= /tmp/evaluation/278784-1169289252/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278784-1169289252/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-278784-1169289252 -o ROOT/results/node2/solver-278784-1169289252 -C 2400 -M 900  /tmp/evaluation/278784-1169289252/cspfj.sh -solver MinConflicts -max -competition /tmp/evaluation/278784-1169289252/unknown.xml

META MD5SUM SOLVER= ae5901f6cce23734dab709fa25e92adb
MD5SUM BENCH=  4bd19d83ae616f3d7b9a2b3141b34394

RANDOM SEED= 921071009

TIME LIMIT= 2400 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.259
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	: 5931.00
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.259
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:       1215232 kB
Buffers:         48020 kB
Cached:         642696 kB
SwapCached:        572 kB
Active:         229548 kB
Inactive:       537400 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1215232 kB
SwapTotal:     4192956 kB
SwapFree:      4180552 kB
Dirty:             476 kB
Writeback:           0 kB
Mapped:          97896 kB
Slab:            58332 kB
Committed_AS:  8403868 kB
PageTables:       2492 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= 66563 MiB



End job on node2 on Sat Jan 20 10:34:19 UTC 2007