Trace number 240224

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, and are wall clock time (not CPU 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
VALCSP 3.0SAT 13.6489 13.7202

DiagnosticValue
CHECKS196085000
NODES450168

General information on the benchmark

Nameqcp-qwh/QCP-20/
qcp-20-187-6_ext.xml
MD5SUM96ec8cf1b7a7943c03a06ad57432798a
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 benchmark3.19751
SatisfiableYES
(Un)Satisfiability was proved
Number of variables400
Number of constraints7600
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension7600
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

13.71	s SATISFIABLE
13.71	v 0 3 17 18 15 14 7 2 12 4 8 9 19 6 5 11 16 1 10 13 10 6 16 17 4 8 3 14 1 11 7 13 9 5 12 0 15 19 18 2 1 16 15 5 10 11 12 9 18 2 19 14 17 3 0 6 8 13 4 7 14 0 7 16 3 15 11 8 17 13 12 5 6 19 18 9 2 4 1 10 2 19 10 3 11 16 6 13 9 17 1 12 8 7 4 14 18 15 0 5 7 1 8 4 14 12 17 3 11 16 18 6 5 13 19 10 0 2 15 9 15 11 4 6 7 9 13 17 8 1 3 16 2 18 14 5 12 10 19 0 6 2 11 7 13 18 0 19 3 5 10 15 12 17 8 1 4 9 14 16 5 9 0 15 1 19 4 18 16 8 6 10 7 11 2 13 17 12 3 14 9 4 18 10 2 3 5 0 15 12 14 1 16 8 13 19 7 11 6 17 13 15 9 12 16 7 8 10 19 6 17 11 0 4 1 3 14 5 2 18 16 8 19 13 12 4 1 6 2 14 0 18 15 9 17 7 10 3 5 11 12 5 14 9 19 17 2 1 0 7 15 4 3 16 10 18 11 6 13 8 11 17 12 2 8 13 19 15 14 18 4 7 1 10 3 16 5 0 9 6 3 12 13 14 18 2 10 7 5 9 16 0 4 15 6 17 1 8 11 19 8 14 5 0 6 1 15 4 13 19 11 17 10 2 7 12 9 18 16 3 19 10 1 8 17 5 18 11 6 0 9 2 13 12 16 15 3 14 7 4 17 18 6 1 9 0 16 5 10 3 2 19 11 14 15 4 13 7 8 12 18 7 3 19 5 10 9 16 4 15 13 8 14 0 11 2 6 17 12 1 4 13 2 11 0 6 14 12 7 10 5 3 18 1 9 8 19 16 17 15 
13.71	d CHECKS 1.96085e+08
13.71	d NODES 450168
13.71

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node10/watcher-240224-1168370896 -o ROOT/results/node10/solver-240224-1168370896 -C 1800 -M 900 /tmp/evaluation/240224-1168370896/VALCSP /tmp/evaluation/240224-1168370896/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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.105805 s]
/proc/loadavg: 1.72 1.93 1.89 5/89 30574
/proc/meminfo: memFree=1753304/2055920 swapFree=4178216/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 1.72 1.93 1.89 5/89 30574
/proc/meminfo: memFree=1753304/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=7400 CPUtime=0.09
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 1558 0 0 0 9 0 0 0 20 0 1 0 185484746 7577600 1536 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 9348522 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 1850 1536 64 8 0 1522 0

[startup+0.513862 s]
/proc/loadavg: 1.72 1.93 1.89 5/89 30574
/proc/meminfo: memFree=1753304/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=12696 CPUtime=0.5
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 2918 0 0 0 49 1 0 0 24 0 1 0 185484746 13000704 2896 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524629 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 3174 2896 66 8 0 2846 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 12696

[startup+1.33498 s]
/proc/loadavg: 1.72 1.93 1.89 3/89 30574
/proc/meminfo: memFree=1742808/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=12696 CPUtime=1.32
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 2918 0 0 0 131 1 0 0 25 0 1 0 185484746 13000704 2896 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524781 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 3174 2896 66 8 0 2846 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 12696

[startup+2.9722 s]
/proc/loadavg: 1.74 1.94 1.89 3/89 30574
/proc/meminfo: memFree=1742808/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=12696 CPUtime=2.95
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 2918 0 0 0 294 1 0 0 25 0 1 0 185484746 13000704 2896 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524789 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 3174 2896 66 8 0 2846 0
Current children cumulated CPU time (s) 2.95
Current children cumulated vsize (KiB) 12696

[startup+6.25165 s]
/proc/loadavg: 1.74 1.94 1.89 3/89 30574
/proc/meminfo: memFree=1742744/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=12696 CPUtime=6.21
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 2918 0 0 0 620 1 0 0 25 0 1 0 185484746 13000704 2896 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524776 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 3174 2896 66 8 0 2846 0
Current children cumulated CPU time (s) 6.21
Current children cumulated vsize (KiB) 12696

[startup+12.7195 s]
/proc/loadavg: 1.78 1.94 1.90 3/89 30574
/proc/meminfo: memFree=1742744/2055920 swapFree=4178216/4192956
[pid=30573] ppid=30571 vsize=12696 CPUtime=12.65
/proc/30573/stat : 30573 (VALCSP) R 30571 30573 30518 0 -1 4194304 2918 0 0 0 1264 1 0 0 25 0 1 0 185484746 13000704 2896 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524683 0 0 4096 0 0 0 0 17 1 0 0
/proc/30573/statm: 3174 2896 66 8 0 2846 0
Current children cumulated CPU time (s) 12.65
Current children cumulated vsize (KiB) 12696

Child status: 0
Real time (s): 13.7202
CPU time (s): 13.6489
CPU user time (s): 13.6319
CPU system time (s): 0.016997
CPU usage (%): 99.4807
Max. virtual memory (cumulated for all children) (KiB): 12696

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

runsolver used 0.026995 s user time and 0.041993 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 19:28:16 UTC 2007


IDJOB= 240224
IDBENCH= 7114
FILE ID= node10/240224-1168370896

PBS_JOBID= 3503866

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/qcp-qwh/QCP-20/qcp-20-187-6_ext.xml
COMMAND LINE= /tmp/evaluation/240224-1168370896/VALCSP /tmp/evaluation/240224-1168370896/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-240224-1168370896 -o ROOT/results/node10/solver-240224-1168370896 -C 1800 -M 900  /tmp/evaluation/240224-1168370896/VALCSP /tmp/evaluation/240224-1168370896/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  96ec8cf1b7a7943c03a06ad57432798a

RANDOM SEED= 627735752

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.232
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.232
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:       1754616 kB
Buffers:         58136 kB
Cached:         142928 kB
SwapCached:       2596 kB
Active:         138404 kB
Inactive:       106660 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1754616 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:             788 kB
Writeback:           0 kB
Mapped:          54316 kB
Slab:            41164 kB
Committed_AS:  5378864 kB
PageTables:       2216 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= 66560 MiB



End job on node10 on Tue Jan  9 19:28:30 UTC 2007