Trace number 2079862

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.178971 0.179098

DiagnosticValue
ASSIGNMENTS214
CHECKS106669
NODES214

General information on the benchmark

Namecsp/travellingSalesman-20/
normalized-tsp-20-1_ext.xml
MD5SUM9cc3eb9ba37c3015a0a8ff5ed022e4f0
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.178971
Satisfiable
(Un)Satisfiability was proved
Number of variables61
Number of constraints230
Maximum constraint arity3
Maximum domain size1001
Number of constraints which are defined in extension230
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.00	c mistral version 1.545
0.10/0.16	s SATISFIABLE
0.10/0.16	v 16 7 3 3 18 16 12 15 19 17 9 0 5 5 4 11 8 2 14 1 13 2 10 3 15 7 7 26 1 0 2 18 6 0 17 3 20 15 11 9 10 26 41 58 58 63 74 76 77 79 82 89 115 115 133 133 136 151 160 160 0
0.10/0.16	d CHECKS 106669
0.10/0.16	d ASSIGNMENTS 214
0.10/0.16	d NODES 214 BACKTRACKS 202 FAILURES 202 RUNTIME 0.09 TOTALTIME 0.16 NODES/s 2377.78 CHECKS/s 1.18521e+06

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-2079862-1247368987/watcher-2079862-1247368987 -o /tmp/evaluation-result-2079862-1247368987/solver-2079862-1247368987 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2079862-1247368987.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: 2.00 2.05 2.07 4/83 23298
/proc/meminfo: memFree=1383824/2055920 swapFree=4192812/4192956
[pid=23298] ppid=23296 vsize=4804 CPUtime=0
/proc/23298/stat : 23298 (ld-linux.so.2) R 23296 23298 20092 0 -1 4194304 226 0 0 0 0 0 0 0 18 0 1 0 23965072 4919296 205 996147200 1448431616 1448550632 4294956208 18446744073709551615 4159670240 0 0 4096 0 0 0 0 17 0 0 0
/proc/23298/statm: 1201 217 185 29 0 16 0

[startup+0.032271 s]
/proc/loadavg: 2.00 2.05 2.07 4/83 23298
/proc/meminfo: memFree=1383824/2055920 swapFree=4192812/4192956
[pid=23298] ppid=23296 vsize=6712 CPUtime=0.02
/proc/23298/stat : 23298 (ld-linux.so.2) R 23296 23298 20092 0 -1 4194304 904 0 0 0 2 0 0 0 18 0 1 0 23965072 6873088 883 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/23298/statm: 1678 885 399 29 0 493 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 6712

[startup+0.102281 s]
/proc/loadavg: 2.00 2.05 2.07 4/83 23298
/proc/meminfo: memFree=1383824/2055920 swapFree=4192812/4192956
[pid=23298] ppid=23296 vsize=13720 CPUtime=0.1
/proc/23298/stat : 23298 (ld-linux.so.2) R 23296 23298 20092 0 -1 4194304 2686 0 0 0 9 1 0 0 18 0 1 0 23965072 14049280 2665 996147200 1448431616 1448550632 4294956208 18446744073709551615 134850107 0 0 4096 0 0 0 0 17 0 0 0
/proc/23298/statm: 3430 2665 425 29 0 2245 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 13720

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

Child status: 0
Real time (s): 0.179098
CPU time (s): 0.178971
CPU user time (s): 0.164974
CPU system time (s): 0.013997
CPU usage (%): 99.929
Max. virtual memory (cumulated for all children) (KiB): 13720

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.164974
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2738
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= 14
involuntary context switches= 10

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node26 at 2009-07-12 05:23:07
IDJOB=2079862
IDBENCH=56965
IDSOLVER=769
FILE ID=node26/2079862-1247368987
PBS_JOBID= 9507081
Free space on /tmp= 66396 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/travellingSalesman-20/normalized-tsp-20-1_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-2079862-1247368987/watcher-2079862-1247368987 -o /tmp/evaluation-result-2079862-1247368987/solver-2079862-1247368987 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2079862-1247368987.xml

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

MD5SUM BENCH= 9cc3eb9ba37c3015a0a8ff5ed022e4f0
RANDOM SEED=959646959

node26.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.281
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.281
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:       1384304 kB
Buffers:         45608 kB
Cached:         279772 kB
SwapCached:          0 kB
Active:         417916 kB
Inactive:       177404 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1384304 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1948 kB
Writeback:           0 kB
Mapped:         285548 kB
Slab:            61128 kB
Committed_AS:   866780 kB
PageTables:       2228 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= 66396 MiB
End job on node26 at 2009-07-12 05:23:08