Trace number 2056960

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
Mistral 1.545SAT 0.344946 0.407966

DiagnosticValue
ASSIGNMENTS0
CHECKS496
NODES0

General information on the benchmark

Namecsp/hanoi/
normalized-hanoi-7_ext.xml
MD5SUMeb96c548468c2556d48ce74fccf574fa
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.326949
Satisfiable
(Un)Satisfiability was proved
Number of variables126
Number of constraints125
Maximum constraint arity2
Maximum domain size2187
Number of constraints which are defined in extension125
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.06	c mistral version 1.545
0.33/0.40	s SATISFIABLE
0.33/0.40	v 2 5 4 22 21 24 26 53 52 46 45 36 38 41 40 202 201 204 206 197 196 190 189 216 218 221 220 238 237 240 242 485 484 478 477 468 470 473 472 418 417 420 422 413 412 406 405 324 326 329 328 346 345 348 350 377 376 370 369 360 362 365 364 1822 1821 1824 1826 1817 1816 1810 1809 1836 1838 1841 1840 1858 1857 1860 1862 1781 1780 1774 1773 1764 1766 1769 1768 1714 1713 1716 1718 1709 1708 1702 1701 1944 1946 1949 1948 1966 1965 1968 1970 1997 1996 1990 1989 1980 1982 1985 1984 2146 2145 2148 2150 2141 2140 2134 2133 2160 2162 2165 2164 2182 2181 2184
0.33/0.40	d CHECKS 496
0.33/0.40	d ASSIGNMENTS 0
0.33/0.40	d NODES 0 BACKTRACKS 0 FAILURES 0 RUNTIME 0.07 TOTALTIME 0.33 NODES/s 0 CHECKS/s 7085.71

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2056960-1247317686/watcher-2056960-1247317686 -o /tmp/evaluation-result-2056960-1247317686/solver-2056960-1247317686 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2056960-1247317686.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 0.06 0.08 0.03 3/68 14428
/proc/meminfo: memFree=1210248/2055920 swapFree=4192952/4192956
[pid=14428] ppid=14426 vsize=2224 CPUtime=0
/proc/14428/stat : 14428 (ld-linux.so.2) D 14426 14428 14266 0 -1 4194304 47 0 1 0 0 0 0 0 20 0 1 0 18834035 2277376 33 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448525284 0 0 4096 0 18446744071563608240 0 0 17 1 0 0
/proc/14428/statm: 556 33 25 29 0 4 0

[startup+0.082081 s]
/proc/loadavg: 0.06 0.08 0.03 3/68 14428
/proc/meminfo: memFree=1210248/2055920 swapFree=4192952/4192956
[pid=14428] ppid=14426 vsize=5356 CPUtime=0.01
/proc/14428/stat : 14428 (ld-linux.so.2) R 14426 14428 14266 0 -1 4194304 555 0 7 0 1 0 0 0 18 0 1 0 18834035 5484544 541 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/14428/statm: 1372 548 379 29 0 187 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5356

[startup+0.101083 s]
/proc/loadavg: 0.06 0.08 0.03 3/68 14428
/proc/meminfo: memFree=1210248/2055920 swapFree=4192952/4192956
[pid=14428] ppid=14426 vsize=8836 CPUtime=0.03
/proc/14428/stat : 14428 (ld-linux.so.2) R 14426 14428 14266 0 -1 4194304 1420 0 7 0 3 0 0 0 18 0 1 0 18834035 9048064 1406 996147200 1448431616 1448550632 4294956208 18446744073709551615 134777670 0 0 4096 0 0 0 0 17 0 0 0
/proc/14428/statm: 2209 1406 392 29 0 1024 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 8836

[startup+0.301118 s]
/proc/loadavg: 0.06 0.08 0.03 3/68 14428
/proc/meminfo: memFree=1210248/2055920 swapFree=4192952/4192956
[pid=14428] ppid=14426 vsize=10476 CPUtime=0.23
/proc/14428/stat : 14428 (ld-linux.so.2) R 14426 14428 14266 0 -1 4194304 1848 0 7 0 23 0 0 0 20 0 1 0 18834035 10727424 1834 996147200 1448431616 1448550632 4294956208 18446744073709551615 135264152 0 0 4096 0 0 0 0 17 0 0 0
/proc/14428/statm: 2619 1834 392 29 0 1434 0
Current children cumulated CPU time (s) 0.23
Current children cumulated vsize (KiB) 10476

Solver just ended. Dumping a history of the last processes samples

[startup+0.401137 s]
/proc/loadavg: 0.06 0.08 0.03 3/68 14428
/proc/meminfo: memFree=1210248/2055920 swapFree=4192952/4192956
[pid=14428] ppid=14426 vsize=10880 CPUtime=0.33
/proc/14428/stat : 14428 (ld-linux.so.2) R 14426 14428 14266 0 -1 4194304 1952 0 7 0 33 0 0 0 20 0 1 0 18834035 11141120 1938 996147200 1448431616 1448550632 4294956208 18446744073709551615 135277704 0 0 4096 0 0 0 0 17 0 0 0
/proc/14428/statm: 2720 1938 405 29 0 1535 0
Current children cumulated CPU time (s) 0.33
Current children cumulated vsize (KiB) 10880

Child status: 0
Real time (s): 0.407966
CPU time (s): 0.344946
CPU user time (s): 0.335948
CPU system time (s): 0.008998
CPU usage (%): 84.5527
Max. virtual memory (cumulated for all children) (KiB): 10880

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

runsolver used 0.001999 second user time and 0.011998 second system time

The end

Launcher Data 

Begin job on node84 at 2009-07-11 15:08:07
IDJOB=2056960
IDBENCH=53321
IDSOLVER=769
FILE ID=node84/2056960-1247317686
PBS_JOBID= 9506467
Free space on /tmp= 66296 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/hanoi/normalized-hanoi-7_ext.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2056960-1247317686/watcher-2056960-1247317686 -o /tmp/evaluation-result-2056960-1247317686/solver-2056960-1247317686 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2056960-1247317686.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= eb96c548468c2556d48ce74fccf574fa
RANDOM SEED=759418780

node84.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1210728 kB
Buffers:         35772 kB
Cached:         721948 kB
SwapCached:          4 kB
Active:         117488 kB
Inactive:       655024 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1210728 kB
SwapTotal:     4192956 kB
SwapFree:      4192952 kB
Dirty:            1236 kB
Writeback:           0 kB
Mapped:          24560 kB
Slab:            58384 kB
Committed_AS:   107504 kB
PageTables:       1572 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= 66292 MiB
End job on node84 at 2009-07-11 15:08:07