Trace number 203934

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.694893 0.706747

DiagnosticValue
CHECKS104505000
NODES300

General information on the benchmark

Namedomino/
domino-300-100.xml
MD5SUMeff2a61155581d1c1ba66ec540fd5989
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.028995
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables300
Number of constraints300
Maximum constraint arity2
Maximum domain size100
Number of constraints which are defined in extension0
Number of constraints which are defined in intension300
Global constraints used (with number of constraints)

Solver Data (download as text)

0.70	s SATISFIABLE
0.70	v 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 
0.70	d CHECKS 1.04505e+08
0.70	d NODES 300
0.70

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-203934-1168165043 -o ROOT/results/node10/solver-203934-1168165043 -C 1800 -M 900 /tmp/evaluation/203934-1168165043/VALCSP /tmp/evaluation/203934-1168165043/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.50 1.86 1.95 5/86 29132
/proc/meminfo: memFree=1524888/2055920 swapFree=4178216/4192956
[pid=29131] ppid=29129 vsize=1384 CPUtime=0
/proc/29131/stat : 29131 (VALCSP) R 29129 29131 28794 0 -1 4194304 53 0 0 0 0 0 0 0 21 0 1 0 164899581 1417216 38 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 8909831 0 0 4096 0 0 0 0 17 1 0 0
/proc/29131/statm: 346 38 30 8 0 6 0

[startup+0.104304 s]
/proc/loadavg: 1.50 1.86 1.95 5/86 29132
/proc/meminfo: memFree=1524888/2055920 swapFree=4178216/4192956
[pid=29131] ppid=29129 vsize=12160 CPUtime=0.09
/proc/29131/stat : 29131 (VALCSP) R 29129 29131 28794 0 -1 4194304 2777 0 0 0 9 0 0 0 21 0 1 0 164899581 12451840 2755 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530207 0 0 4096 0 0 0 0 17 1 0 0
/proc/29131/statm: 3040 2755 64 8 0 2712 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12160

[startup+0.51236 s]
/proc/loadavg: 1.50 1.86 1.95 5/86 29132
/proc/meminfo: memFree=1524888/2055920 swapFree=4178216/4192956
[pid=29131] ppid=29129 vsize=15988 CPUtime=0.49
/proc/29131/stat : 29131 (VALCSP) R 29129 29131 28794 0 -1 4194304 3744 0 0 0 48 1 0 0 25 0 1 0 164899581 16371712 3722 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134522170 0 0 4096 0 0 0 0 17 1 0 0
/proc/29131/statm: 3997 3722 66 8 0 3669 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 15988

Child status: 0
Real time (s): 0.706747
CPU time (s): 0.694893
CPU user time (s): 0.677896
CPU system time (s): 0.016997
CPU usage (%): 98.3227
Max. virtual memory (cumulated for all children) (KiB): 15988

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.677896
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= 3774
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= 30

runsolver used 0.004999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Sun Jan  7 10:17:25 UTC 2007


IDJOB= 203934
IDBENCH= 3990
FILE ID= node10/203934-1168165043

PBS_JOBID= 3478322

Free space on /tmp= 66374 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-300-100.xml
COMMAND LINE= /tmp/evaluation/203934-1168165043/VALCSP /tmp/evaluation/203934-1168165043/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-203934-1168165043 -o ROOT/results/node10/solver-203934-1168165043 -C 1800 -M 900  /tmp/evaluation/203934-1168165043/VALCSP /tmp/evaluation/203934-1168165043/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  eff2a61155581d1c1ba66ec540fd5989

RANDOM SEED= 344761968

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:       1525368 kB
Buffers:         54972 kB
Cached:         354952 kB
SwapCached:       2088 kB
Active:         121572 kB
Inactive:       324720 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1525368 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:             564 kB
Writeback:           0 kB
Mapped:          49312 kB
Slab:            69152 kB
Committed_AS:  3996144 kB
PageTables:       2180 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= 66374 MiB



End job on node10 on Sun Jan  7 10:17:25 UTC 2007