Trace number 224540

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 1.9897 2.00914

DiagnosticValue
CHECKS10204600
NODES287

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-55_ext.xml
MD5SUM1d88273099d17cdf7189ddf176c61d43
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 benchmark1.64775
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.00	s SATISFIABLE
2.00	v 1 18 6 78 24 44 62 3 62 24 22 34 5 7 24 42 78 13 28 50 12 35 10 36 64 54 70 9 3 40 62 62 53 1 28 3 24 4 54 2 
2.00	d CHECKS 1.02046e+07
2.00	d NODES 287
2.00

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/node33/watcher-224540-1168269130 -o ROOT/results/node33/solver-224540-1168269130 -C 1800 -M 900 /tmp/evaluation/224540-1168269130/VALCSP /tmp/evaluation/224540-1168269130/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: 2.01 1.98 1.99 5/74 17802
/proc/meminfo: memFree=656464/2055920 swapFree=4192224/4192956
[pid=17801] ppid=17799 vsize=18540 CPUtime=0
/proc/17801/stat : 17801 (runsolver) R 17799 17801 16432 0 -1 4194368 16 0 0 0 0 0 0 0 21 0 1 0 175306851 18984960 279 18446744073709551615 4194304 4267372 548682069088 18446744073709551615 210824129831 0 0 4096 24578 0 0 0 17 1 0 0
/proc/17801/statm: 4635 279 244 17 0 2626 0

[startup+0.156952 s]
/proc/loadavg: 2.01 1.98 1.99 5/74 17802
/proc/meminfo: memFree=656464/2055920 swapFree=4192224/4192956
[pid=17801] ppid=17799 vsize=1864 CPUtime=0.14
/proc/17801/stat : 17801 (VALCSP) R 17799 17801 16432 0 -1 4194304 206 0 0 0 14 0 0 0 21 0 1 0 175306851 1908736 184 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 11406556 0 0 4096 0 0 0 0 17 1 0 0
/proc/17801/statm: 466 184 62 8 0 138 0
Current children cumulated CPU time (s) 0.14
Current children cumulated vsize (KiB) 1864

[startup+0.565036 s]
/proc/loadavg: 2.01 1.98 1.99 5/74 17802
/proc/meminfo: memFree=656464/2055920 swapFree=4192224/4192956
[pid=17801] ppid=17799 vsize=2788 CPUtime=0.55
/proc/17801/stat : 17801 (VALCSP) R 17799 17801 16432 0 -1 4194304 434 0 0 0 55 0 0 0 25 0 1 0 175306851 2854912 412 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 11409302 0 0 4096 0 0 0 0 17 1 0 0
/proc/17801/statm: 697 412 62 8 0 369 0
Current children cumulated CPU time (s) 0.55
Current children cumulated vsize (KiB) 2788

[startup+1.38921 s]
/proc/loadavg: 2.00 1.98 1.99 3/74 17802
/proc/meminfo: memFree=653584/2055920 swapFree=4192224/4192956
[pid=17801] ppid=17799 vsize=4636 CPUtime=1.36
/proc/17801/stat : 17801 (VALCSP) R 17799 17801 16432 0 -1 4194304 901 0 0 0 136 0 0 0 25 0 1 0 175306851 4747264 879 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 11388228 0 0 4096 0 0 0 0 17 1 0 0
/proc/17801/statm: 1159 879 62 8 0 831 0
Current children cumulated CPU time (s) 1.36
Current children cumulated vsize (KiB) 4636

Child status: 0
Real time (s): 2.00914
CPU time (s): 1.9897
CPU user time (s): 1.9817
CPU system time (s): 0.007998
CPU usage (%): 99.0321
Max. virtual memory (cumulated for all children) (KiB): 8332

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

runsolver used 0.001999 s user time and 0.010998 s system time

The end

Launcher Data (download as text)

Begin job on node33 on Mon Jan  8 15:12:10 UTC 2007


IDJOB= 224540
IDBENCH= 5763
FILE ID= node33/224540-1168269130

PBS_JOBID= 3482854

Free space on /tmp= 66561 MiB

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

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  1d88273099d17cdf7189ddf176c61d43

RANDOM SEED= 758093017

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.281
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.281
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:        656880 kB
Buffers:          3496 kB
Cached:        1272600 kB
SwapCached:        264 kB
Active:         590716 kB
Inactive:       757968 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        656880 kB
SwapTotal:     4192956 kB
SwapFree:      4192224 kB
Dirty:            1088 kB
Writeback:           0 kB
Mapped:          83476 kB
Slab:            35528 kB
Committed_AS:  3424660 kB
PageTables:       1856 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= 66561 MiB



End job on node33 on Mon Jan  8 15:12:12 UTC 2007