Trace number 284069

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
rjw-solver 2007-01-21SAT 0.331948 0.340179

DiagnosticValue
CHECKS77374
NODES53

General information on the benchmark

Namegeom/
geo50-20-d4-75-100_ext.xml
MD5SUM169fb451f2076ddc22f6e7641b848e1a
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 benchmark0.113981
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints393
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension393
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.33	v 1 1 14 1 19 10 7 7 4 3 4 1 2 1 3 15 17 10 14 1 8 1 11 2 14 14 11 1 18 8 17 15 5 4 1 14 4 9 8 13 1 17 16 2 4 7 8 2 10 2 
0.33	s SATISFIABLE
0.33	d NODES 53
0.33	d CHECKS 77374
c 
c 
c 
c conversion script
c 
c

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/node76/watcher-284069-1169472104 -o ROOT/results/node76/solver-284069-1169472104 -C 1800 -M 900 /tmp/evaluation/284069-1169472104/solve /tmp/evaluation/284069-1169472104/unknown 1800 

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.63 1.79 1.67 5/80 28097
/proc/meminfo: memFree=1435672/2055888 swapFree=4068452/4096564
[pid=28096] ppid=28094 vsize=5360 CPUtime=0
/proc/28096/stat : 28096 (solve) R 28094 28096 27815 0 -1 4194304 259 0 0 0 0 0 0 0 20 0 1 0 295609378 5488640 226 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 206843736463 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/28096/statm: 1340 226 189 169 0 50 0
[pid=28098] ppid=28096 vsize=5360 CPUtime=0
/proc/28098/stat : 28098 (solve) R 28096 28096 27815 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 295609378 5488640 226 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 206843736463 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/28098/statm: 1340 226 189 169 0 50 0

[startup+0.103146 s]
/proc/loadavg: 1.63 1.79 1.67 5/80 28097
/proc/meminfo: memFree=1435672/2055888 swapFree=4068452/4096564
[pid=28096] ppid=28094 vsize=5360 CPUtime=0
/proc/28096/stat : 28096 (solve) S 28094 28096 27815 0 -1 4194304 313 168 0 0 0 0 0 0 20 0 1 0 295609378 5488640 227 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 206843734596 0 65536 4100 65538 18446744071563358023 0 0 17 0 0 0
/proc/28096/statm: 1340 227 190 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5360

Child status: 0
Real time (s): 0.340179
CPU time (s): 0.331948
CPU user time (s): 0.32295
CPU system time (s): 0.008998
CPU usage (%): 97.5804
Max. virtual memory (cumulated for all children) (KiB): 5360

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.32295
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1624
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= 40
involuntary context switches= 13

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Mon Jan 22 13:21:47 UTC 2007


IDJOB= 284069
IDBENCH= 6489
IDSOLVER= 93
FILE ID= node76/284069-1169472104

PBS_JOBID= 3613924

Free space on /tmp= 66650 MiB

SOLVER NAME= rjw-solver 2007-01-21
BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-100_ext.xml
COMMAND LINE= /tmp/evaluation/284069-1169472104/solve /tmp/evaluation/284069-1169472104/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-284069-1169472104 -o ROOT/results/node76/conversion-284069-1169472104 -C 600 -M 900 /tmp/evaluation/284069-1169472104/conversion /tmp/evaluation/284069-1169472104/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-284069-1169472104 -o ROOT/results/node76/solver-284069-1169472104 -C 1800 -M 900  /tmp/evaluation/284069-1169472104/solve /tmp/evaluation/284069-1169472104/unknown 1800

META MD5SUM SOLVER= 4108942ff566d5523369442a8e3d06c4
MD5SUM BENCH=  169fb451f2076ddc22f6e7641b848e1a

RANDOM SEED= 381964443

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1436152 kB
Buffers:         11292 kB
Cached:         543884 kB
SwapCached:      21940 kB
Active:         308700 kB
Inactive:       283612 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1436152 kB
SwapTotal:     4096564 kB
SwapFree:      4068452 kB
Dirty:            1184 kB
Writeback:           0 kB
Mapped:          25188 kB
Slab:            13060 kB
Committed_AS:  8472248 kB
PageTables:       1804 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66650 MiB



End job on node76 on Mon Jan 22 13:22:05 UTC 2007