Trace number 224502

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.48562 2.50078

DiagnosticValue
CHECKS41054200
NODES1405

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-39_ext.xml
MD5SUM3cd4b239a65fb95cf015560cf326b561
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.48562
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints103
Maximum constraint arity2
Maximum domain size80
Number of constraints which are defined in extension103
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

2.49	s SATISFIABLE
2.49	v 3 44 57 16 70 2 5 3 10 68 31 61 31 76 46 23 56 7 34 0 34 21 70 41 4 55 77 12 52 10 14 78 37 26 21 59 74 66 28 58 
2.49	d CHECKS 4.10542e+07
2.49	d NODES 1405
2.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/node47/watcher-224502-1168269007 -o ROOT/results/node47/solver-224502-1168269007 -C 1800 -M 900 /tmp/evaluation/224502-1168269007/VALCSP /tmp/evaluation/224502-1168269007/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.78 1.95 1.90 5/85 8103
/proc/meminfo: memFree=1583464/2055920 swapFree=4183964/4192956
[pid=8102] ppid=8100 vsize=1468 CPUtime=0
/proc/8102/stat : 8102 (VALCSP) R 8100 8102 7991 0 -1 4194304 125 0 0 0 0 0 0 0 20 0 1 0 175299985 1503232 103 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 10978390 0 0 4096 0 0 0 0 17 1 0 0
/proc/8102/statm: 367 103 62 8 0 39 0

[startup+0.108389 s]
/proc/loadavg: 1.78 1.95 1.90 5/85 8103
/proc/meminfo: memFree=1583464/2055920 swapFree=4183964/4192956
[pid=8102] ppid=8100 vsize=1732 CPUtime=0.1
/proc/8102/stat : 8102 (VALCSP) R 8100 8102 7991 0 -1 4194304 175 0 0 0 10 0 0 0 20 0 1 0 175299985 1773568 153 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 10980524 0 0 4096 0 0 0 0 17 1 0 0
/proc/8102/statm: 433 153 62 8 0 105 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1732

[startup+0.516431 s]
/proc/loadavg: 1.78 1.95 1.90 5/85 8103
/proc/meminfo: memFree=1583464/2055920 swapFree=4183964/4192956
[pid=8102] ppid=8100 vsize=2660 CPUtime=0.51
/proc/8102/stat : 8102 (VALCSP) R 8100 8102 7991 0 -1 4194304 414 0 0 0 51 0 0 0 24 0 1 0 175299985 2723840 392 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 10980526 0 0 4096 0 0 0 0 17 1 0 0
/proc/8102/statm: 665 392 62 8 0 337 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 2660

[startup+1.33752 s]
/proc/loadavg: 1.78 1.95 1.90 3/85 8103
/proc/meminfo: memFree=1580776/2055920 swapFree=4183964/4192956
[pid=8102] ppid=8100 vsize=4512 CPUtime=1.32
/proc/8102/stat : 8102 (VALCSP) R 8100 8102 7991 0 -1 4194304 880 0 0 0 132 0 0 0 25 0 1 0 175299985 4620288 858 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 10980526 0 0 4096 0 0 0 0 17 1 0 0
/proc/8102/statm: 1128 858 62 8 0 800 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 4512

Child status: 0
Real time (s): 2.50078
CPU time (s): 2.48562
CPU user time (s): 2.47862
CPU system time (s): 0.006998
CPU usage (%): 99.3937
Max. virtual memory (cumulated for all children) (KiB): 8340

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

runsolver used 0.003999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node47 on Mon Jan  8 15:10:07 UTC 2007


IDJOB= 224502
IDBENCH= 5756
FILE ID= node47/224502-1168269007

PBS_JOBID= 3482956

Free space on /tmp= 66556 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-39_ext.xml
COMMAND LINE= /tmp/evaluation/224502-1168269007/VALCSP /tmp/evaluation/224502-1168269007/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node47/watcher-224502-1168269007 -o ROOT/results/node47/solver-224502-1168269007 -C 1800 -M 900  /tmp/evaluation/224502-1168269007/VALCSP /tmp/evaluation/224502-1168269007/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  3cd4b239a65fb95cf015560cf326b561

RANDOM SEED= 784862527

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.240
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.240
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:       1583944 kB
Buffers:         42188 kB
Cached:         112172 kB
SwapCached:       3468 kB
Active:         339872 kB
Inactive:        77192 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1583944 kB
SwapTotal:     4192956 kB
SwapFree:      4183964 kB
Dirty:            1168 kB
Writeback:           0 kB
Mapped:         278108 kB
Slab:            39580 kB
Committed_AS:  4669572 kB
PageTables:       2364 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= 66556 MiB



End job on node47 on Mon Jan  8 15:10:10 UTC 2007