Trace number 1055599

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
mddc-solv 2008-06-09SAT 0.309952 0.316799

DiagnosticValue
CHECKS26705

General information on the benchmark

Namecsp/travellingSalesman-20/
normalized-tsp-20-30_ext.xml
MD5SUM90be3b55b88ef8a1b3d0242fef77e8ed
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.083986
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 (download as text)

0.19/0.20	c loading... 0.17 secs
0.19/0.20	c smallest 5
0.19/0.20	c largest 293
0.19/0.20	c average 32.5217
0.19/0.20	
0.29/0.31	s SATISFIABLE
0.29/0.31	v 7 15 12 2 20 18 16 23 8 1 11 8 4 4 19 1 3 1 14 3 15 6 2 1 18 13 13 2 17 17 6 5 10 14 1 3 9 2 5 5 17 35 58 59 67 71 72 73 76 82 83 96 98 115 120 134 137 139 144 144 0
0.29/0.31	d CHECKS 26705
0.29/0.31	c FAILS 24
0.29/0.31	c RESTARTS 0

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1055599-1215059890/watcher-1055599-1215059890 -o /tmp/evaluation-result-1055599-1215059890/solver-1055599-1215059890 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1055599-1215059890.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): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.94 2.04 2.07 4/72 17682
/proc/meminfo: memFree=1739808/2055920 swapFree=4179444/4192956
[pid=17682] ppid=17680 vsize=364 CPUtime=0
/proc/17682/stat : 17682 (solver) R 17680 17682 12863 0 -1 4194304 39 0 0 0 0 0 0 0 21 0 1 0 1984963835 372736 25 996147200 134512640 134773262 4294956256 18446744073709551615 8905508 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/17682/statm: 91 25 19 63 0 3 0

[startup+0.146192 s]
/proc/loadavg: 1.94 2.04 2.07 4/72 17682
/proc/meminfo: memFree=1739808/2055920 swapFree=4179444/4192956
[pid=17682] ppid=17680 vsize=10588 CPUtime=0.12
/proc/17682/stat : 17682 (solver) R 17680 17682 12863 0 -1 4194304 1914 0 0 0 12 0 0 0 18 0 1 0 1984963835 10842112 1862 996147200 134512640 134773262 4294956256 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/17682/statm: 2647 1862 338 63 0 1664 0
Current children cumulated CPU time (s) 0.12
Current children cumulated vsize (KiB) 10588

[startup+0.20119 s]
/proc/loadavg: 1.94 2.04 2.07 4/72 17682
/proc/meminfo: memFree=1739808/2055920 swapFree=4179444/4192956
[pid=17682] ppid=17680 vsize=6916 CPUtime=0.19
/proc/17682/stat : 17682 (solver) R 17680 17682 12863 0 -1 4194304 2027 0 0 0 18 1 0 0 18 0 1 0 1984963835 7081984 949 996147200 134512640 134773262 4294956256 18446744073709551615 134529952 0 0 4096 0 0 0 0 17 1 0 0
/proc/17682/statm: 1729 949 364 63 0 746 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 6916

[startup+0.301204 s]
/proc/loadavg: 1.94 2.04 2.07 4/72 17682
/proc/meminfo: memFree=1739808/2055920 swapFree=4179444/4192956
[pid=17682] ppid=17680 vsize=6916 CPUtime=0.29
/proc/17682/stat : 17682 (solver) R 17680 17682 12863 0 -1 4194304 2028 0 0 0 28 1 0 0 19 0 1 0 1984963835 7081984 950 996147200 134512640 134773262 4294956256 18446744073709551615 134529747 0 0 4096 0 0 0 0 17 1 0 0
/proc/17682/statm: 1729 950 364 63 0 746 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6916

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

[startup+0.301204 s]
/proc/loadavg: 1.94 2.04 2.07 4/72 17682
/proc/meminfo: memFree=1739808/2055920 swapFree=4179444/4192956
[pid=17682] ppid=17680 vsize=6916 CPUtime=0.29
/proc/17682/stat : 17682 (solver) R 17680 17682 12863 0 -1 4194304 2028 0 0 0 28 1 0 0 19 0 1 0 1984963835 7081984 950 996147200 134512640 134773262 4294956256 18446744073709551615 134529747 0 0 4096 0 0 0 0 17 1 0 0
/proc/17682/statm: 1729 950 364 63 0 746 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6916

Child status: 0
Real time (s): 0.316799
CPU time (s): 0.309952
CPU user time (s): 0.296954
CPU system time (s): 0.012998
CPU usage (%): 97.8386
Max. virtual memory (cumulated for all children) (KiB): 10588

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node10 at 2008-07-03 06:38:10
IDJOB=1055599
IDBENCH=56963
IDSOLVER=311
FILE ID=node10/1055599-1215059890
PBS_JOBID= 7875153
Free space on /tmp= 66528 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/travellingSalesman-20/normalized-tsp-20-30_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1055599-1215059890/watcher-1055599-1215059890 -o /tmp/evaluation-result-1055599-1215059890/solver-1055599-1215059890 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1055599-1215059890.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 90be3b55b88ef8a1b3d0242fef77e8ed
RANDOM SEED=679642738

node10.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.229
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.229
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:       1740288 kB
Buffers:         55756 kB
Cached:         149456 kB
SwapCached:       7560 kB
Active:         149444 kB
Inactive:        90760 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1740288 kB
SwapTotal:     4192956 kB
SwapFree:      4179444 kB
Dirty:             760 kB
Writeback:           0 kB
Mapped:          42304 kB
Slab:            60692 kB
Committed_AS:  3295100 kB
PageTables:       1952 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= 66528 MiB
End job on node10 at 2008-07-03 06:38:10