Trace number 278789

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
Toolbar_BTD 2007-01-12SAT 0.075987 0.0949499

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)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SOL 0 2 4 3 1 2 4 2 0 2 1 4 4 0 4 0 2 1 4 0 0 1 2 2 0 1 4 2 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/278789-1169289258/unknown.xml to /tmp/evaluation/278789-1169289258/unknown.wcsp

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/node24/watcher-278789-1169289258 -o ROOT/results/node24/solver-278789-1169289258 -C 2400 -M 900 /tmp/evaluation/278789-1169289258/solver.sh /tmp/evaluation/278789-1169289258/unknown 

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.38 1.10 1.57 5/83 30411
/proc/meminfo: memFree=1372608/2055920 swapFree=4180096/4192956
[pid=30410] ppid=30407 vsize=8652 CPUtime=0
/proc/30410/stat : 30410 (solver.sh) R 30407 30410 29892 0 -1 4194304 335 0 0 0 0 0 0 0 17 0 1 0 277321758 8859648 279 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 237788261023 0 65538 4096 73728 0 0 0 17 1 0 0
/proc/30410/statm: 2163 279 207 79 0 156 0
[pid=30412] ppid=30410 vsize=8688 CPUtime=0
/proc/30412/stat : 30412 (solver.sh) R 30410 30410 29892 0 -1 4194368 38 0 0 0 0 0 0 0 17 0 1 0 277321758 8896512 286 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 4425865 0 0 4096 73728 0 0 0 17 1 0 0
/proc/30412/statm: 2172 286 209 79 0 165 0
[pid=30413] ppid=30412 vsize=8728 CPUtime=0
/proc/30413/stat : 30413 (solver.sh) R 30412 30410 29892 0 -1 4194368 26 0 0 0 0 0 0 0 20 0 1 0 277321758 8937472 290 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 237788261671 0 0 3674112 73728 0 0 0 17 1 0 0
/proc/30413/statm: 2182 290 209 79 0 175 0

Child status: 0
Real time (s): 0.0949499
CPU time (s): 0.075987
CPU user time (s): 0.033994
CPU system time (s): 0.041993
CPU usage (%): 80.0285
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.033994
system time used= 0.041993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5637
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= 89
involuntary context switches= 44

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Sat Jan 20 10:34:19 UTC 2007


IDJOB= 278789
IDBENCH= 8853
IDSOLVER= 72
FILE ID= node24/278789-1169289258

PBS_JOBID= 3609685

Free space on /tmp= 66560 MiB

SOLVER NAME= Toolbar_BTD 2007-01-12
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/278789-1169289258/solver.sh /tmp/evaluation/278789-1169289258/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node24/convwatcher-278789-1169289258 -o ROOT/results/node24/conversion-278789-1169289258 -C 600 -M 900 /tmp/evaluation/278789-1169289258/translate /tmp/evaluation/278789-1169289258/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-278789-1169289258 -o ROOT/results/node24/solver-278789-1169289258 -C 2400 -M 900  /tmp/evaluation/278789-1169289258/solver.sh /tmp/evaluation/278789-1169289258/unknown

META MD5SUM SOLVER= f75ee5e830002fa98429bd59d9dcbc78
MD5SUM BENCH=  4bd19d83ae616f3d7b9a2b3141b34394

RANDOM SEED= 817833801

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.234
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.234
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:       1373416 kB
Buffers:         45876 kB
Cached:         523432 kB
SwapCached:        600 kB
Active:         165192 kB
Inactive:       449548 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1373416 kB
SwapTotal:     4192956 kB
SwapFree:      4180096 kB
Dirty:            4552 kB
Writeback:           4 kB
Mapped:          62396 kB
Slab:            52716 kB
Committed_AS:  5502328 kB
PageTables:       2196 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= 66560 MiB



End job on node24 on Sat Jan 20 10:34:27 UTC 2007