Trace number 1072969

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-option 1.314SAT 0.153976 0.159658

DiagnosticValue
ASSIGNMENTS1061
CHECKS94027

General information on the benchmark

Namecsp/radar-8-30-3-0/
normalized-radar-8-30-3-0-39.xml
MD5SUM2eb9b079214aab0b9ee1a9355b6b709d
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.047992
Satisfiable
(Un)Satisfiability was proved
Number of variables180
Number of constraints64
Maximum constraint arity18
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension64
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c mistral-option version 1.313
0.09/0.15	s SATISFIABLE
0.09/0.15	v 3 0 0 1 3 1 1 0 0 0 0 1 1 3 0 0 0 3 2 3 0 1 0 0 2 1 0 0 2 2 1 0 3 0 0 2 0 0 0 3 0 3 1 1 1 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 3 3 1 0 0 0 3 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0 3 1 1 2 0 1 3 0 0 1 1 1 3 0 0 0 0 2 0 0 0 0 3 3 0 1 1 0 0 0 2 1 0 0 0 0 3 0 2 0 0 3 0 0 1 1 1 1 3 0 3 3 3 0 3 0 1 2 3 0 2 3 2 2 2 2 1 2 1 1 2 0 0 1 1 1 0 3 3 1 2 3 3 3
0.09/0.15	d CHECKS 94027
0.09/0.15	d ASSIGNMENTS 1061

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-1072969-1215176210/watcher-1072969-1215176210 -o /tmp/evaluation-result-1072969-1215176210/solver-1072969-1215176210 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1072969-1215176210.xml -heu dyn -sac 3 -ds 2 

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: 2.45 2.28 2.11 4/82 31256
/proc/meminfo: memFree=1819224/2055924 swapFree=4177292/4192956
[pid=31256] ppid=31254 vsize=18572 CPUtime=0
/proc/31256/stat : 31256 (runsolver) R 31254 31256 29903 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 673350620 19017728 292 996147200 4194304 4296836 548682068416 18446744073709551615 230266826023 0 0 4096 24578 0 0 0 17 1 0 0
/proc/31256/statm: 4643 292 257 25 0 2626 0

[startup+0.034654 s]
/proc/loadavg: 2.45 2.28 2.11 4/82 31256
/proc/meminfo: memFree=1819224/2055924 swapFree=4177292/4192956
[pid=31256] ppid=31254 vsize=4992 CPUtime=0.02
/proc/31256/stat : 31256 (xsolve) R 31254 31256 29903 0 -1 4194304 556 0 0 0 2 0 0 0 20 0 1 0 673350620 5111808 522 996147200 134512640 135239763 4294956192 18446744073709551615 134706823 0 0 4096 0 0 0 0 17 0 0 0
/proc/31256/statm: 1248 522 375 177 0 151 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 4992

[startup+0.101674 s]
/proc/loadavg: 2.45 2.28 2.11 4/82 31256
/proc/meminfo: memFree=1819224/2055924 swapFree=4177292/4192956
[pid=31256] ppid=31254 vsize=6580 CPUtime=0.09
/proc/31256/stat : 31256 (xsolve) R 31254 31256 29903 0 -1 4194304 1004 0 0 0 9 0 0 0 20 0 1 0 673350620 6737920 970 996147200 134512640 135239763 4294956192 18446744073709551615 134833888 0 0 4096 0 0 0 0 17 0 0 0
/proc/31256/statm: 1645 970 411 177 0 548 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6580

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

Child status: 0
Real time (s): 0.159658
CPU time (s): 0.153976
CPU user time (s): 0.147977
CPU system time (s): 0.005999
CPU usage (%): 96.4412
Max. virtual memory (cumulated for all children) (KiB): 6580

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.147977
system time used= 0.005999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1021
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= 9

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node83 at 2008-07-04 14:56:50
IDJOB=1072969
IDBENCH=56302
IDSOLVER=357
FILE ID=node83/1072969-1215176210
PBS_JOBID= 7881531
Free space on /tmp= 66552 MiB

SOLVER NAME= Mistral-option 1.314
BENCH NAME= CPAI08/csp/radar-8-30-3-0/normalized-radar-8-30-3-0-39.xml
COMMAND LINE= HOME/xsolve BENCHNAME -heu dyn -sac 3 -ds 2 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1072969-1215176210/watcher-1072969-1215176210 -o /tmp/evaluation-result-1072969-1215176210/solver-1072969-1215176210 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1072969-1215176210.xml -heu dyn -sac 3 -ds 2 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 2eb9b079214aab0b9ee1a9355b6b709d
RANDOM SEED=1735174618

node83.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.263
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.263
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:      2055924 kB
MemFree:       1819768 kB
Buffers:         19652 kB
Cached:         112384 kB
SwapCached:       9336 kB
Active:         164944 kB
Inactive:        27760 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1819768 kB
SwapTotal:     4192956 kB
SwapFree:      4177292 kB
Dirty:            4512 kB
Writeback:           0 kB
Mapped:          75232 kB
Slab:            28664 kB
Committed_AS:  1820384 kB
PageTables:       1940 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= 66552 MiB
End job on node83 at 2008-07-04 14:56:51