Trace number 279358

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
aolibpvo 2007-01-17OPTIMUM 2.27065 2.28164

General information on the benchmark

NameMaxCSP/kbtree/kbtree-9-2-3-5/kbtree-9-2-3-5-30/
kbtree-9-2-3-5-30-11_ext.xml
MD5SUM7f860c7c06c69375dc1bcdfdb1b2370b
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints304
Best CPU time to get the best result obtained on this benchmark2.27065
Satisfiable
(Un)Satisfiability was proved
Number of variables58
Number of constraints309
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension309
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)

2.27	
2.27	s SATISFIABLE
2.27	o 296
2.27	v 4 4 2 1 3 4 4 4 0 1 4 3 4 3 4 3 0 1 4 4 0 2 1 1 0 0 2 1 2 2 3 4 4 3 0 3 2 0 1 2 3 1 1 1 0 2 4 0 0 0 4 0 4 3 1 0 3 2
2.27	s SATISFIABLE
2.27	o 297
2.27	v 4 4 2 1 3 4 4 4 0 1 4 3 4 3 4 3 0 1 4 4 0 2 1 1 0 0 2 1 2 2 3 4 2 3 0 3 2 0 1 2 3 1 1 1 0 2 4 0 0 0 4 0 4 3 1 0 3 2
2.27	s SATISFIABLE
2.27	o 298
2.27	v 4 4 2 1 3 4 4 4 0 1 4 2 1 4 1 3 0 2 4 4 2 0 4 1 4 4 4 1 0 3 2 4 4 0 0 3 2 0 1 2 3 1 1 1 0 2 4 0 0 0 4 0 4 3 1 0 3 2
2.27	s SATISFIABLE
2.27	o 299
2.27	v 4 4 2 1 3 4 4 4 0 1 3 2 1 4 1 3 0 2 4 4 2 0 4 4 4 4 4 1 0 3 2 4 4 0 0 3 2 0 1 2 3 1 1 1 0 2 4 0 0 0 4 0 4 3 1 0 3 2
2.27	s SATISFIABLE
2.27	o 300
2.27	v 4 4 2 2 4 4 3 4 1 1 3 2 1 4 1 3 0 2 4 1 1 0 4 4 4 4 4 1 0 3 2 4 4 0 0 3 2 0 1 2 3 1 1 1 0 2 4 0 0 0 4 0 4 3 1 0 3 2
2.27	s SATISFIABLE
2.27	o 302
2.27	v 3 4 2 2 4 4 3 4 1 1 3 2 1 4 1 3 0 2 4 4 2 0 4 1 4 4 4 1 0 3 2 4 4 0 1 3 2 3 4 2 1 1 2 1 1 2 4 1 1 1 4 0 4 1 3 2 3 3
2.27	s SATISFIABLE
2.27	o 303
2.27	v 0 3 3 3 2 3 2 3 0 1 3 2 1 4 1 3 0 2 4 4 2 0 2 4 1 2 4 1 0 3 2 4 4 0 0 3 3 0 4 4 1 1 2 1 4 1 1 3 1 2 4 1 2 2 1 4 4 4
2.27	s SATISFIABLE
2.27	o 304
2.27	v 0 3 3 3 2 3 2 3 0 1 3 2 1 4 1 3 0 2 4 4 2 0 2 4 1 2 4 1 0 3 2 4 4 0 0 3 3 0 3 4 3 1 3 1 0 1 4 0 4 0 4 1 2 2 2 4 2 4
2.27	o 304
2.27	v 0 3 3 3 2 3 2 3 0 1 3 2 1 4 1 3 0 2 4 4 2 0 2 4 1 2 4 1 0 3 2 4 4 0 0 3 3 0 3 4 3 1 3 1 0 1 4 0 4 0 4 1 2 2 2 4 2 4
2.27	s OPTIMUM FOUND
c 
c 
c 
c conversion script
c 
c 

parsing "/tmp/evaluation/279358-1169292700/unknown.xml" file ... done.
writing "/tmp/evaluation/279358-1169292700/unknown.wcsp" file ... done.

Verifier Data (download as text)

5 unsatisfied constraints, 304 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/node76/watcher-279358-1169292700 -o ROOT/results/node76/solver-279358-1169292700 -C 2400 -M 900 /tmp/evaluation/279358-1169292700/aolibpvo /tmp/evaluation/279358-1169292700/unknown.wcsp 

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: 1.92 1.98 1.90 3/85 6070
/proc/meminfo: memFree=1667496/2055888 swapFree=4087964/4096564
[pid=6069] ppid=6067 vsize=2580 CPUtime=0
/proc/6069/stat : 6069 (aolibpvo) R 6067 6069 5528 0 -1 0 205 0 0 0 0 0 0 0 18 0 1 0 277667143 2641920 187 18446744073709551615 134512640 136266365 4294956720 18446744073709551615 135743014 0 0 4096 0 0 0 0 17 0 0 0
/proc/6069/statm: 645 187 138 428 0 214 0

[startup+0.103022 s]
/proc/loadavg: 1.92 1.98 1.90 3/85 6070
/proc/meminfo: memFree=1667496/2055888 swapFree=4087964/4096564
[pid=6069] ppid=6067 vsize=2712 CPUtime=0.09
/proc/6069/stat : 6069 (aolibpvo) R 6067 6069 5528 0 -1 0 277 0 0 0 9 0 0 0 18 0 1 0 277667143 2777088 259 18446744073709551615 134512640 136266365 4294956720 18446744073709551615 135779552 0 0 4096 0 0 0 0 17 0 0 0
/proc/6069/statm: 678 259 169 428 0 247 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2712

[startup+0.5111 s]
/proc/loadavg: 1.92 1.98 1.90 3/85 6070
/proc/meminfo: memFree=1667496/2055888 swapFree=4087964/4096564
[pid=6069] ppid=6067 vsize=3280 CPUtime=0.5
/proc/6069/stat : 6069 (aolibpvo) R 6067 6069 5528 0 -1 0 464 0 0 0 50 0 0 0 22 0 1 0 277667143 3358720 446 18446744073709551615 134512640 136266365 4294956720 18446744073709551615 134648039 0 0 4096 0 0 0 0 17 0 0 0
/proc/6069/statm: 820 446 199 428 0 389 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 3280

[startup+1.33226 s]
/proc/loadavg: 1.92 1.98 1.90 3/85 6070
/proc/meminfo: memFree=1666536/2055888 swapFree=4087964/4096564
[pid=6069] ppid=6067 vsize=3280 CPUtime=1.32
/proc/6069/stat : 6069 (aolibpvo) R 6067 6069 5528 0 -1 0 464 0 0 0 132 0 0 0 25 0 1 0 277667143 3358720 446 18446744073709551615 134512640 136266365 4294956720 18446744073709551615 135237932 0 0 4096 0 0 0 0 17 0 0 0
/proc/6069/statm: 820 446 199 428 0 389 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 3280

Child status: 0
Real time (s): 2.28164
CPU time (s): 2.27065
CPU user time (s): 2.27065
CPU system time (s): 0
CPU usage (%): 99.5186
Max. virtual memory (cumulated for all children) (KiB): 3280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.27065
system time used= 0
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 469
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 8
involuntary context switches= 77

runsolver used 0.006998 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Sat Jan 20 11:31:40 UTC 2007


IDJOB= 279358
IDBENCH= 9916
IDSOLVER= 60
FILE ID= node76/279358-1169292700

PBS_JOBID= 3609762

Free space on /tmp= 66648 MiB

SOLVER NAME= aolibpvo 2007-01-17
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-9-2-3-5/kbtree-9-2-3-5-30/kbtree-9-2-3-5-30-11_ext.xml
COMMAND LINE= /tmp/evaluation/279358-1169292700/aolibpvo /tmp/evaluation/279358-1169292700/unknown.wcsp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-279358-1169292700 -o ROOT/results/node76/conversion-279358-1169292700 -C 600 -M 900 python xcsp2wcsp.py /tmp/evaluation/279358-1169292700/unknown.xml
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-279358-1169292700 -o ROOT/results/node76/solver-279358-1169292700 -C 2400 -M 900  /tmp/evaluation/279358-1169292700/aolibpvo /tmp/evaluation/279358-1169292700/unknown.wcsp

META MD5SUM SOLVER= b8e99429ba4d9a99d2bd28d3d95367aa
MD5SUM BENCH=  7f860c7c06c69375dc1bcdfdb1b2370b

RANDOM SEED= 484478608

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1668040 kB
Buffers:         25872 kB
Cached:         266508 kB
SwapCached:       2128 kB
Active:         112440 kB
Inactive:       221008 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1668040 kB
SwapTotal:     4096564 kB
SwapFree:      4087964 kB
Dirty:            2176 kB
Writeback:           0 kB
Mapped:          58444 kB
Slab:            40104 kB
Committed_AS:  8804712 kB
PageTables:       1892 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66648 MiB



End job on node76 on Sat Jan 20 11:31:43 UTC 2007