Trace number 1100667

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-noprobe 2008-06-27SAT 0.487925 0.496267

DiagnosticValue
ASSIGNMENTS444
CHECKS104833

General information on the benchmark

Namecsp/tightness0.9/
normalized-rand-2-40-180-84-900-68_ext.xml
MD5SUM05cba7c74125d0bc5638fc16925830e4
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.487925
Satisfiable
(Un)Satisfiability was proved
Number of variables40
Number of constraints84
Maximum constraint arity2
Maximum domain size180
Number of constraints which are defined in extension84
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.20	c mistral-prime version 1.313
0.38/0.47	s SATISFIABLE
0.38/0.47	v 133 110 99 88 135 50 108 48 102 129 56 14 142 99 74 132 6 83 9 5 82 60 59 59 32 0 148 18 56 117 89 117 109 85 143 37 145 49 69 124
0.38/0.47	d CHECKS 104833
0.38/0.47	d ASSIGNMENTS 444

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-1100667-1215287518/watcher-1100667-1215287518 -o /tmp/evaluation-result-1100667-1215287518/solver-1100667-1215287518 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1100667-1215287518.xml -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.04 2.02 2.00 4/81 15380
/proc/meminfo: memFree=1714296/2055920 swapFree=4179860/4192956
[pid=15380] ppid=15378 vsize=820 CPUtime=0
/proc/15380/stat : 15380 (xsolve) R 15378 15380 12723 0 -1 4194304 39 0 0 0 0 0 0 0 19 0 1 0 2007721502 839680 25 996147200 134512640 135239859 4294956208 18446744073709551615 9839396 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/15380/statm: 205 25 19 177 0 3 0

[startup+0.208818 s]
/proc/loadavg: 2.04 2.02 2.00 4/81 15380
/proc/meminfo: memFree=1714296/2055920 swapFree=4179860/4192956
[pid=15380] ppid=15378 vsize=8832 CPUtime=0.19
/proc/15380/stat : 15380 (xsolve) R 15378 15380 12723 0 -1 4194304 1506 0 0 0 19 0 0 0 19 0 1 0 2007721502 9043968 1472 996147200 134512640 135239859 4294956208 18446744073709551615 134579041 0 0 4096 0 0 0 0 17 1 0 0
/proc/15380/statm: 2208 1472 350 177 0 1111 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 8832

[startup+0.302692 s]
/proc/loadavg: 2.04 2.02 2.00 4/81 15380
/proc/meminfo: memFree=1714296/2055920 swapFree=4179860/4192956
[pid=15380] ppid=15378 vsize=11484 CPUtime=0.28
/proc/15380/stat : 15380 (xsolve) R 15378 15380 12723 0 -1 4194304 2201 0 0 0 28 0 0 0 19 0 1 0 2007721502 11759616 2167 996147200 134512640 135239859 4294956208 18446744073709551615 135019157 0 0 4096 0 0 0 0 17 1 0 0
/proc/15380/statm: 2871 2167 386 177 0 1774 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 11484

[startup+0.402697 s]
/proc/loadavg: 2.04 2.02 2.00 4/81 15380
/proc/meminfo: memFree=1714296/2055920 swapFree=4179860/4192956
[pid=15380] ppid=15378 vsize=11488 CPUtime=0.38
/proc/15380/stat : 15380 (xsolve) R 15378 15380 12723 0 -1 4194304 2202 0 0 0 38 0 0 0 20 0 1 0 2007721502 11763712 2168 996147200 134512640 135239859 4294956208 18446744073709551615 135019073 0 0 4096 0 0 0 0 17 1 0 0
/proc/15380/statm: 2872 2168 386 177 0 1775 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 11488

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

[startup+0.402697 s]
/proc/loadavg: 2.04 2.02 2.00 4/81 15380
/proc/meminfo: memFree=1714296/2055920 swapFree=4179860/4192956
[pid=15380] ppid=15378 vsize=11488 CPUtime=0.38
/proc/15380/stat : 15380 (xsolve) R 15378 15380 12723 0 -1 4194304 2202 0 0 0 38 0 0 0 20 0 1 0 2007721502 11763712 2168 996147200 134512640 135239859 4294956208 18446744073709551615 135019073 0 0 4096 0 0 0 0 17 1 0 0
/proc/15380/statm: 2872 2168 386 177 0 1775 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 11488

Child status: 0
Real time (s): 0.496267
CPU time (s): 0.487925
CPU user time (s): 0.479927
CPU system time (s): 0.007998
CPU usage (%): 98.319
Max. virtual memory (cumulated for all children) (KiB): 11488

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

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node66 at 2008-07-05 21:51:58
IDJOB=1100667
IDBENCH=59961
IDSOLVER=343
FILE ID=node66/1100667-1215287518
PBS_JOBID= 7882228
Free space on /tmp= 66416 MiB

SOLVER NAME= MDG-noprobe 2008-06-27
BENCH NAME= CPAI08/csp/tightness0.9/normalized-rand-2-40-180-84-900-68_ext.xml
COMMAND LINE= HOME/xsolve BENCHNAME -heu dom/wdeg -res no 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1100667-1215287518/watcher-1100667-1215287518 -o /tmp/evaluation-result-1100667-1215287518/solver-1100667-1215287518 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1100667-1215287518.xml -heu dom/wdeg -res no 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 05cba7c74125d0bc5638fc16925830e4
RANDOM SEED=1462059914

node66.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.213
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.213
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:       1714776 kB
Buffers:         52832 kB
Cached:         198696 kB
SwapCached:       7144 kB
Active:         193356 kB
Inactive:        92952 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1714776 kB
SwapTotal:     4192956 kB
SwapFree:      4179860 kB
Dirty:            3012 kB
Writeback:           0 kB
Mapped:          50812 kB
Slab:            39800 kB
Committed_AS:  4194808 kB
PageTables:       1948 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= 66416 MiB
End job on node66 at 2008-07-05 21:51:59