Trace number 279233

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
aolibdvo 2007-01-17SAT 0.081986 0.0895249

General information on the benchmark

NameMaxCSP/kbtree/kbtree-9-5-3-5/kbtree-9-5-3-5-10/
kbtree-9-5-3-5-10-11_ext.xml
MD5SUM0240748faf11fccbe78eebd68af57859
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints255
Best CPU time to get the best result obtained on this benchmark0.077987
SatisfiableYES
(Un)Satisfiability was proved
Number of variables40
Number of constraints255
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension255
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.08	
0.08	s SATISFIABLE
0.08	o 253
0.08	v 4 3 4 4 4 3 4 4 4 2 4 4 4 3 3 4 4 3 4 3 4 2 4 4 4 2 4 4 1 4 4 4 4 4 4 4 4 4 4 3
0.08	s SATISFIABLE
0.08	o 254
0.08	v 4 0 4 4 4 2 4 4 4 2 4 4 4 2 3 4 4 3 4 3 4 2 4 4 4 2 4 4 1 4 4 4 4 4 4 4 4 4 4 3
0.08	s SATISFIABLE
0.08	o 255
0.08	v 4 2 4 3 4 2 2 4 4 1 4 4 4 2 3 4 4 3 4 3 4 2 4 4 4 2 4 4 1 4 3 4 4 4 4 4 4 4 4 3
0.08	o 255
0.08	v 4 2 4 3 4 2 2 4 4 1 4 4 4 2 3 4 4 3 4 3 4 2 4 4 4 2 4 4 1 4 3 4 4 4 4 4 4 4 4 3
0.08	s OPTIMUM FOUND
c 
c 
c 
c conversion script
c 
c 

parsing "/tmp/evaluation/279233-1169291820/unknown.xml" file ... done.
writing "/tmp/evaluation/279233-1169291820/unknown.wcsp" file ... done.

Verifier Data (download as text)

0 unsatisfied constraints, 255 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/node3/watcher-279233-1169291820 -o ROOT/results/node3/solver-279233-1169291820 -C 2400 -M 900 /tmp/evaluation/279233-1169291820/aolibdvo /tmp/evaluation/279233-1169291820/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.84 1.94 1.90 5/93 32358
/proc/meminfo: memFree=1275552/2055920 swapFree=4191880/4192956
[pid=32357] ppid=32355 vsize=18540 CPUtime=0
/proc/32357/stat : 32357 (runsolver) R 32355 32357 31646 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 277577838 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 233632754983 0 0 4096 24578 0 0 0 17 1 0 0
/proc/32357/statm: 4635 279 244 17 0 2626 0

Child status: 0
Real time (s): 0.0895249
CPU time (s): 0.081986
CPU user time (s): 0.080987
CPU system time (s): 0.000999
CPU usage (%): 91.579
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.080987
system time used= 0.000999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 415
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= 4

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node3 on Sat Jan 20 11:17:00 UTC 2007


IDJOB= 279233
IDBENCH= 9666
IDSOLVER= 61
FILE ID= node3/279233-1169291820

PBS_JOBID= 3609564

Free space on /tmp= 66561 MiB

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

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node3/watcher-279233-1169291820 -o ROOT/results/node3/solver-279233-1169291820 -C 2400 -M 900  /tmp/evaluation/279233-1169291820/aolibdvo /tmp/evaluation/279233-1169291820/unknown.wcsp

META MD5SUM SOLVER= 5d0282fabcfebd5fb942c79c8af6ce28
MD5SUM BENCH=  0240748faf11fccbe78eebd68af57859

RANDOM SEED= 686211682

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.279
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.279
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:       1276032 kB
Buffers:         56884 kB
Cached:         564352 kB
SwapCached:        284 kB
Active:         221776 kB
Inactive:       482420 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1276032 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            2248 kB
Writeback:           0 kB
Mapped:         104708 kB
Slab:            60640 kB
Committed_AS:  8448516 kB
PageTables:       2160 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 node3 on Sat Jan 20 11:17:02 UTC 2007