Trace number 227743

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 2.37564 2.40156

DiagnosticValue
CHECKS75128200
NODES23413

General information on the benchmark

Nametightness/tightness0.1/
rand-2-40-8-753-100-19_ext.xml
MD5SUM2dc54fc58f8f656ca6898d0651b3f1c0
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 benchmark2.37564
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints753
Maximum constraint arity2
Maximum domain size8
Number of constraints which are defined in extension753
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

2.39	s SATISFIABLE
2.39	v 2 5 3 6 2 7 0 6 0 4 0 7 6 0 1 0 7 6 0 3 0 2 2 2 5 0 0 0 0 3 0 3 5 3 1 6 0 0 0 5 
2.39	d CHECKS 7.51282e+07
2.39	d NODES 23413
2.39

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/node2/watcher-227743-1168278781 -o ROOT/results/node2/solver-227743-1168278781 -C 1800 -M 900 /tmp/evaluation/227743-1168278781/VALCSP /tmp/evaluation/227743-1168278781/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.71 1.87 1.97 5/98 16897
/proc/meminfo: memFree=1629760/2055920 swapFree=4191880/4192956
[pid=16896] ppid=16894 vsize=18540 CPUtime=0
/proc/16896/stat : 16896 (runsolver) R 16894 16896 16788 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 176273824 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 206381313319 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16896/statm: 4635 279 244 17 0 2626 0

[startup+0.10816 s]
/proc/loadavg: 1.71 1.87 1.97 5/98 16897
/proc/meminfo: memFree=1629760/2055920 swapFree=4191880/4192956
[pid=16896] ppid=16894 vsize=2524 CPUtime=0.09
/proc/16896/stat : 16896 (VALCSP) R 16894 16896 16788 0 -1 4194304 393 0 0 0 9 0 0 0 20 0 1 0 176273824 2584576 371 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524658 0 0 4096 0 0 0 0 17 1 0 0
/proc/16896/statm: 631 371 65 8 0 303 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2524

[startup+0.517234 s]
/proc/loadavg: 1.71 1.87 1.97 5/98 16897
/proc/meminfo: memFree=1629760/2055920 swapFree=4191880/4192956
[pid=16896] ppid=16894 vsize=2524 CPUtime=0.5
/proc/16896/stat : 16896 (VALCSP) R 16894 16896 16788 0 -1 4194304 393 0 0 0 50 0 0 0 24 0 1 0 176273824 2584576 371 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524602 0 0 4096 0 0 0 0 17 1 0 0
/proc/16896/statm: 631 371 65 8 0 303 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 2524

[startup+1.34138 s]
/proc/loadavg: 1.71 1.87 1.97 3/98 16897
/proc/meminfo: memFree=1628480/2055920 swapFree=4191880/4192956
[pid=16896] ppid=16894 vsize=2524 CPUtime=1.32
/proc/16896/stat : 16896 (VALCSP) R 16894 16896 16788 0 -1 4194304 393 0 0 0 132 0 0 0 25 0 1 0 176273824 2584576 371 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524781 0 0 4096 0 0 0 0 17 1 0 0
/proc/16896/statm: 631 371 65 8 0 303 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 2524

Child status: 0
Real time (s): 2.40156
CPU time (s): 2.37564
CPU user time (s): 2.37064
CPU system time (s): 0.004999
CPU usage (%): 98.9207
Max. virtual memory (cumulated for all children) (KiB): 2524

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

runsolver used 0.005999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Mon Jan  8 17:53:02 UTC 2007


IDJOB= 227743
IDBENCH= 6109
FILE ID= node2/227743-1168278781

PBS_JOBID= 3483156

Free space on /tmp= 66339 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.1/rand-2-40-8-753-100-19_ext.xml
COMMAND LINE= /tmp/evaluation/227743-1168278781/VALCSP /tmp/evaluation/227743-1168278781/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-227743-1168278781 -o ROOT/results/node2/solver-227743-1168278781 -C 1800 -M 900  /tmp/evaluation/227743-1168278781/VALCSP /tmp/evaluation/227743-1168278781/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  2dc54fc58f8f656ca6898d0651b3f1c0

RANDOM SEED= 913183138

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.259
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	: 5931.00
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.259
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:       1630240 kB
Buffers:         42972 kB
Cached:         157000 kB
SwapCached:        288 kB
Active:         297236 kB
Inactive:        79248 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1630240 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             348 kB
Writeback:           0 kB
Mapped:         204816 kB
Slab:            33644 kB
Committed_AS:  5370124 kB
PageTables:       2656 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= 66339 MiB



End job on node2 on Mon Jan  8 17:53:04 UTC 2007