Trace number 195521

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.485925 0.499003

DiagnosticValue
CHECKS2692900
NODES400

General information on the benchmark

Namerlfap/rlfapGraphs/
graph4.xml
MD5SUM13ba5fc23607aef5e34106e0ee22f4bd
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.872866
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2244
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2244
Global constraints used (with number of constraints)

Solver Data (download as text)

0.49	s SATISFIABLE
0.49	v 58 296 16 254 114 352 44 282 652 414 156 394 722 484 114 352 16 254 142 380 764 526 100 338 142 380 72 310 114 352 652 414 142 380 128 366 16 254 100 338 114 352 750 512 652 414 44 282 86 324 58 296 114 352 142 380 778 540 58 296 128 366 128 366 30 268 58 296 128 366 512 750 44 282 750 512 156 394 736 498 114 352 16 254 44 282 16 254 16 254 764 526 142 380 156 394 652 414 142 380 764 526 16 254 86 324 156 394 666 428 156 394 114 352 142 380 778 540 86 324 100 338 128 366 142 380 778 540 750 512 736 498 30 268 100 338 86 324 128 366 100 338 72 310 30 268 16 254 44 282 58 296 44 282 156 394 156 394 86 324 114 352 16 254 736 498 44 282 156 394 156 394 114 352 694 456 16 254 694 456 44 282 16 254 86 324 30 268 778 540 128 366 268 30 722 484 764 526 142 380 100 338 30 268 58 296 30 268 72 310 142 380 680 442 652 414 114 352 156 394 736 498 100 338 128 366 114 352 30 268 30 268 694 456 128 366 44 282 72 310 16 254 58 296 114 352 58 296 30 268 128 366 736 498 652 414 72 310 694 456 16 254 764 526 100 338 156 394 484 722 736 498 680 442 352 114 86 324 16 254 156 394 72 310 736 498 156 394 72 310 156 394 142 380 16 254 666 428 30 268 114 352 86 324 72 310 142 380 44 282 736 498 128 366 666 428 750 512 16 254 708 470 156 394 86 324 30 268 44 282 764 526 414 652 142 380 58 296 100 338 666 428 128 366 16 254 30 268 156 394 30 268 736 498 778 540 778 540 694 456 30 268 86 324 722 484 736 498 792 554 30 268 764 526 750 512 128 366 722 484 16 254 44 282 142 380 100 338 30 268 16 254 652 414 652 414 16 254 30 268 
0.49	d CHECKS 2.6929e+06
0.49	d NODES 400
0.49

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/node7/watcher-195521-1168113095 -o ROOT/results/node7/solver-195521-1168113095 -C 1800 -M 900 /tmp/evaluation/195521-1168113095/VALCSP /tmp/evaluation/195521-1168113095/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.88 1.80 1.89 5/94 30054
/proc/meminfo: memFree=881496/2055920 swapFree=4192812/4192956
[pid=30053] ppid=30051 vsize=18540 CPUtime=0
/proc/30053/stat : 30053 (runsolver) R 30051 30053 29632 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 159705062 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 244671114535 0 0 4096 24578 0 0 0 17 1 0 0
/proc/30053/statm: 4635 279 244 17 0 2626 0

[startup+0.103344 s]
/proc/loadavg: 1.88 1.80 1.89 5/94 30054
/proc/meminfo: memFree=881496/2055920 swapFree=4192812/4192956
[pid=30053] ppid=30051 vsize=7144 CPUtime=0.09
/proc/30053/stat : 30053 (VALCSP) R 30051 30053 29632 0 -1 4194304 1531 0 0 0 9 0 0 0 18 0 1 0 159705062 7315456 1509 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530796 0 0 4096 0 0 0 0 17 0 0 0
/proc/30053/statm: 1786 1509 64 8 0 1458 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7144

Child status: 0
Real time (s): 0.499003
CPU time (s): 0.485925
CPU user time (s): 0.462929
CPU system time (s): 0.022996
CPU usage (%): 97.3792
Max. virtual memory (cumulated for all children) (KiB): 18524

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

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node7 on Sat Jan  6 19:51:35 UTC 2007


IDJOB= 195521
IDBENCH= 3284
FILE ID= node7/195521-1168113095

PBS_JOBID= 3477113

Free space on /tmp= 66529 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph4.xml
COMMAND LINE= /tmp/evaluation/195521-1168113095/VALCSP /tmp/evaluation/195521-1168113095/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-195521-1168113095 -o ROOT/results/node7/solver-195521-1168113095 -C 1800 -M 900  /tmp/evaluation/195521-1168113095/VALCSP /tmp/evaluation/195521-1168113095/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  13ba5fc23607aef5e34106e0ee22f4bd

RANDOM SEED= 291210473

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.220
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.220
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:        902520 kB
Buffers:         82688 kB
Cached:         518840 kB
SwapCached:          0 kB
Active:         776328 kB
Inactive:       272508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        902520 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           22020 kB
Writeback:           0 kB
Mapped:         471936 kB
Slab:            88432 kB
Committed_AS:  5020188 kB
PageTables:       3196 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= 66529 MiB



End job on node7 on Sat Jan  6 19:51:37 UTC 2007