Trace number 205003

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 0.559914 0.567308

DiagnosticValue
CHECKS15448200
NODES4544

General information on the benchmark

Namerandom/rand-2-30-15/
rand-2-30-15-306-230-47_ext.xml
MD5SUM191a56b2b22e58cb8db99dd438f8ba02
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.559914
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables30
Number of constraints228
Maximum constraint arity2
Maximum domain size15
Number of constraints which are defined in extension228
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.56	s SATISFIABLE
0.56	v 7 2 11 13 10 4 10 12 13 6 14 11 6 3 5 12 1 3 2 1 6 13 5 13 3 2 9 9 6 8 
0.56	d CHECKS 1.54482e+07
0.56	d NODES 4544
0.56

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/node12/watcher-205003-1168167097 -o ROOT/results/node12/solver-205003-1168167097 -C 1800 -M 900 /tmp/evaluation/205003-1168167097/VALCSP /tmp/evaluation/205003-1168167097/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

/proc/loadavg: 1.33 1.78 1.96 3/94 29522
/proc/meminfo: memFree=980696/2055920 swapFree=4160348/4192956
[pid=29521] ppid=29519 vsize=1384 CPUtime=0
/proc/29521/stat : 29521 (VALCSP) R 29519 29521 29110 0 -1 4194304 73 0 0 0 0 0 0 0 20 0 1 0 165105345 1417216 57 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 9665376 0 0 4096 0 0 0 0 17 1 0 0
/proc/29521/statm: 346 57 46 8 0 6 0

[startup+0.103749 s]
/proc/loadavg: 1.33 1.78 1.96 3/94 29522
/proc/meminfo: memFree=980696/2055920 swapFree=4160348/4192956
[pid=29521] ppid=29519 vsize=2260 CPUtime=0.09
/proc/29521/stat : 29521 (VALCSP) R 29519 29521 29110 0 -1 4194304 324 0 0 0 9 0 0 0 20 0 1 0 165105345 2314240 302 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524796 0 0 4096 0 0 0 0 17 1 0 0
/proc/29521/statm: 565 302 65 8 0 237 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2260

[startup+0.511819 s]
/proc/loadavg: 1.33 1.78 1.96 3/94 29522
/proc/meminfo: memFree=980696/2055920 swapFree=4160348/4192956
[pid=29521] ppid=29519 vsize=2260 CPUtime=0.5
/proc/29521/stat : 29521 (VALCSP) R 29519 29521 29110 0 -1 4194304 324 0 0 0 50 0 0 0 24 0 1 0 165105345 2314240 302 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134524787 0 0 4096 0 0 0 0 17 1 0 0
/proc/29521/statm: 565 302 65 8 0 237 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 2260

Child status: 0
Real time (s): 0.567308
CPU time (s): 0.559914
CPU user time (s): 0.557915
CPU system time (s): 0.001999
CPU usage (%): 98.6967
Max. virtual memory (cumulated for all children) (KiB): 2260

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Sun Jan  7 10:51:42 UTC 2007


IDJOB= 205003
IDBENCH= 4095
FILE ID= node12/205003-1168167097

PBS_JOBID= 3478720

Free space on /tmp= 66319 MiB

BENCH NAME= HOME/pub/bench/CPAI06/random/rand-2-30-15/rand-2-30-15-306-230-47_ext.xml
COMMAND LINE= /tmp/evaluation/205003-1168167097/VALCSP /tmp/evaluation/205003-1168167097/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-205003-1168167097 -o ROOT/results/node12/solver-205003-1168167097 -C 1800 -M 900  /tmp/evaluation/205003-1168167097/VALCSP /tmp/evaluation/205003-1168167097/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  191a56b2b22e58cb8db99dd438f8ba02

RANDOM SEED= 471578796

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.265
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.265
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:        981432 kB
Buffers:         54896 kB
Cached:         525720 kB
SwapCached:       4660 kB
Active:         507248 kB
Inactive:       491852 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        981432 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:         437280 kB
Slab:            59500 kB
Committed_AS:  5282980 kB
PageTables:       2936 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= 66319 MiB



End job on node12 on Sun Jan  7 10:51:44 UTC 2007