Trace number 1103812

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
MDG-probe 2008-06-27SAT 0.270958 0.278218

DiagnosticValue
ASSIGNMENTS4244
CHECKS723496

General information on the benchmark

Namecsp/bqwh-15-106/
normalized-bqwh-15-106-85_ext.xml
MD5SUM2ebc2a324dafcefc371668aefc226ad9
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.064989
Satisfiable
(Un)Satisfiability was proved
Number of variables106
Number of constraints590
Maximum constraint arity2
Maximum domain size6
Number of constraints which are defined in extension590
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.03	c mistral-prime version 1.313
0.00/0.03	c 
0.00/0.03	c Parsing xml file
0.00/0.03	c          domains...............     0	(104 domains)
0.00/0.03	c          variables.............     0	(106 variables)
0.00/0.03	c          relations.............     0	(159 relations)
0.00/0.03	c          constraints...........  0.01	(590 constraints)
0.00/0.03	c Parsing time:   0.01
0.00/0.03	c
0.00/0.03	c Building model
0.00/0.03	c        65 AllDifferent constraints infered
0.00/0.03	c         0 constants
0.00/0.03	c         0 Boolean variables    (+0)
0.00/0.03	c         0 range variables      (+0)
0.00/0.03	c         0 domain (b) variables (+0)
0.00/0.03	c       106 domain (l) variables (+0)
0.00/0.03	c       590 constraints          (+65)
0.00/0.03	c         0 values 
0.00/0.03	c Building time:   0.01
0.00/0.03	c
0.00/0.03	c Solving instance
0.00/0.03	c          heuristic = dom/wdeg
0.00/0.03	c          Randomized probing iteration = 100
0.00/0.03	c          probing limit = 30
0.00/0.03	c          level based weights = no
0.00/0.03	c          impact probing = no
0.00/0.03	c          restart policy = No restart
0.00/0.03	c          probing ..........  0.22
0.19/0.25	c          Probing Nodes  3940
0.19/0.25	c          final run   0.02
0.19/0.27	c Solving time:   0.24
0.19/0.27	c
0.19/0.27	s SATISFIABLE
0.19/0.27	v 7 9 4 0 1 8 14 7 8 6 12 11 13 3 12 6 8 5 7 3 4 14 1 3 12 6 9 13 14 10 8 11 2 0 5 0 2 14 9 3 8 5 5 12 7 3 4 8 6 0 3 4 8 14 7 9 5 14 10 6 7 1 0 11 10 5 4 2 12 0 9 4 1 3 7 12 0 6 0 7 12 14 13 2 6 1 10 7 13 4 5 13 11 5 6 14 1 3 10 3 2 6 4 0 11 1
0.19/0.27	d CHECKS 723496
0.19/0.27	d ASSIGNMENTS 4244

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-1103812-1215301190/watcher-1103812-1215301190 -o /tmp/evaluation-result-1103812-1215301190/solver-1103812-1215301190 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1103812-1215301190.xml -v 1 -rs 864032793 -probe 1 -ph 0 -heu dom/wdeg -res no 

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.20 2.05 2.01 4/81 28385
/proc/meminfo: memFree=1709640/2055920 swapFree=4180232/4192956
[pid=28385] ppid=28383 vsize=18572 CPUtime=0
/proc/28385/stat : 28385 (runsolver) R 28383 28385 27381 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 653056171 19017728 292 996147200 4194304 4296836 548682068336 18446744073709551615 226913479975 0 0 4096 24578 0 0 0 17 1 0 0
/proc/28385/statm: 4643 292 257 25 0 2626 0

[startup+0.031826 s]
/proc/loadavg: 2.20 2.05 2.01 4/81 28385
/proc/meminfo: memFree=1709640/2055920 swapFree=4180232/4192956
[pid=28385] ppid=28383 vsize=5256 CPUtime=0.02
/proc/28385/stat : 28385 (xsolve) R 28383 28385 27381 0 -1 4194304 673 0 0 0 2 0 0 0 19 0 1 0 653056171 5382144 639 996147200 134512640 135239859 4294956144 18446744073709551615 135095152 0 0 4096 0 0 0 0 17 1 0 0
/proc/28385/statm: 1314 639 418 177 0 217 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5256

[startup+0.102493 s]
/proc/loadavg: 2.20 2.05 2.01 4/81 28385
/proc/meminfo: memFree=1709640/2055920 swapFree=4180232/4192956
[pid=28385] ppid=28383 vsize=5256 CPUtime=0.09
/proc/28385/stat : 28385 (xsolve) R 28383 28385 27381 0 -1 4194304 674 0 0 0 9 0 0 0 19 0 1 0 653056171 5382144 640 996147200 134512640 135239859 4294956144 18446744073709551615 134821141 0 0 4096 0 0 0 0 17 1 0 0
/proc/28385/statm: 1314 640 418 177 0 217 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5256

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

[startup+0.202511 s]
/proc/loadavg: 2.20 2.05 2.01 4/81 28385
/proc/meminfo: memFree=1709640/2055920 swapFree=4180232/4192956
[pid=28385] ppid=28383 vsize=5256 CPUtime=0.19
/proc/28385/stat : 28385 (xsolve) R 28383 28385 27381 0 -1 4194304 674 0 0 0 19 0 0 0 20 0 1 0 653056171 5382144 640 996147200 134512640 135239859 4294956144 18446744073709551615 135030997 0 0 4096 0 0 0 0 17 1 0 0
/proc/28385/statm: 1314 640 418 177 0 217 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 5256

Child status: 0
Real time (s): 0.278218
CPU time (s): 0.270958
CPU user time (s): 0.270958
CPU system time (s): 0
CPU usage (%): 97.3905
Max. virtual memory (cumulated for all children) (KiB): 5256

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

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node5 at 2008-07-06 01:39:50
IDJOB=1103812
IDBENCH=60524
IDSOLVER=342
FILE ID=node5/1103812-1215301190
PBS_JOBID= 7882471
Free space on /tmp= 66536 MiB

SOLVER NAME= MDG-probe 2008-06-27
BENCH NAME= CPAI08/csp/bqwh-15-106/normalized-bqwh-15-106-85_ext.xml
COMMAND LINE= HOME/xsolve BENCHNAME -v 1 -rs RANDOMSEED -probe 1 -ph 0 -heu dom/wdeg -res no
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1103812-1215301190/watcher-1103812-1215301190 -o /tmp/evaluation-result-1103812-1215301190/solver-1103812-1215301190 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1103812-1215301190.xml -v 1 -rs 864032793 -probe 1 -ph 0 -heu dom/wdeg -res no

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 2ebc2a324dafcefc371668aefc226ad9
RANDOM SEED=864032793

node5.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.279
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.279
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:       1710120 kB
Buffers:         70404 kB
Cached:         193136 kB
SwapCached:       6964 kB
Active:         195908 kB
Inactive:        93852 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1710120 kB
SwapTotal:     4192956 kB
SwapFree:      4180232 kB
Dirty:            1584 kB
Writeback:           0 kB
Mapped:          41964 kB
Slab:            41188 kB
Committed_AS:  1108752 kB
PageTables:       1864 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= 66532 MiB
End job on node5 at 2008-07-06 01:39:51