Trace number 279067

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_MaxSat 2007-01-19SAT 0.299953 0.378528

General information on the benchmark

NameMaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-20/
kbtree-5-2-4-5-20-01_ext.xml
MD5SUMb90bdf2da85cfad1e9adcfec29c9c182
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints211
Best CPU time to get the best result obtained on this benchmark0.090985
SatisfiableYES
(Un)Satisfiability was proved
Number of variables62
Number of constraints211
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension211
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 1 3 3 3 0 1 4 4 1 4 0 2 2 0 0 0 2 1 3 0 0 1 0 3 4 4 2 0 2 1 1 0 0 0 1 1 0 4 3 2 2 2 3 0 0 0 0 0 4 3 0 1 3 1 0 0 0 2 0 0 1 0 
OPTIMUM
c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/279067-1169291301/unknown.xml to /tmp/evaluation/279067-1169291301/unknown.wcsp

Verifier Data (download as text)

0 unsatisfied constraints, 211 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/node18/watcher-279067-1169291301 -o ROOT/results/node18/solver-279067-1169291301 -C 2400 -M 900 /tmp/evaluation/279067-1169291301/solver.sh /tmp/evaluation/279067-1169291301/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: 1.72 1.95 1.89 5/93 17298
/proc/meminfo: memFree=1265160/2055920 swapFree=4192812/4192956
[pid=17297] ppid=17295 vsize=8560 CPUtime=0
/proc/17297/stat : 17297 (solver.sh) R 17295 17297 16932 0 -1 4194304 308 0 0 0 0 0 0 0 20 0 1 0 277524835 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 227848996751 0 0 4096 8192 0 0 0 17 1 0 0
/proc/17297/statm: 2140 253 197 79 0 133 0

[startup+0.107088 s]
/proc/loadavg: 1.72 1.95 1.89 5/93 17298
/proc/meminfo: memFree=1265160/2055920 swapFree=4192812/4192956
[pid=17297] ppid=17295 vsize=47568 CPUtime=0.01
/proc/17297/stat : 17297 (solver.sh) S 17295 17297 16932 0 -1 4194304 906 2469 0 0 0 0 0 1 22 0 1 0 277524835 48709632 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 227848416090 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/17297/statm: 11892 362 246 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47568

Child status: 0
Real time (s): 0.378528
CPU time (s): 0.299953
CPU user time (s): 0.205968
CPU system time (s): 0.093985
CPU usage (%): 79.242
Max. virtual memory (cumulated for all children) (KiB): 47568

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.205968
system time used= 0.093985
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 17430
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= 112
involuntary context switches= 52

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node18 on Sat Jan 20 11:08:21 UTC 2007


IDJOB= 279067
IDBENCH= 9371
IDSOLVER= 71
FILE ID= node18/279067-1169291301

PBS_JOBID= 3609594

Free space on /tmp= 66561 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-20/kbtree-5-2-4-5-20-01_ext.xml
COMMAND LINE= /tmp/evaluation/279067-1169291301/solver.sh /tmp/evaluation/279067-1169291301/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node18/convwatcher-279067-1169291301 -o ROOT/results/node18/conversion-279067-1169291301 -C 600 -M 900 /tmp/evaluation/279067-1169291301/translate /tmp/evaluation/279067-1169291301/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node18/watcher-279067-1169291301 -o ROOT/results/node18/solver-279067-1169291301 -C 2400 -M 900  /tmp/evaluation/279067-1169291301/solver.sh /tmp/evaluation/279067-1169291301/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  b90bdf2da85cfad1e9adcfec29c9c182

RANDOM SEED= 385920935

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.231
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.231
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:       1265576 kB
Buffers:         53744 kB
Cached:         569680 kB
SwapCached:          0 kB
Active:         280296 kB
Inactive:       429308 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1265576 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2192 kB
Writeback:           0 kB
Mapped:         115276 kB
Slab:            65428 kB
Committed_AS:  9734588 kB
PageTables:       2180 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 node18 on Sat Jan 20 11:08:22 UTC 2007