Trace number 230335

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
Mistral 2006-12-04SAT 0.148977 0.149423

General information on the benchmark

Namegeom/
geo50-20-d4-75-97_ext.xml
MD5SUM58b6187a22c96037a9bcdd1cf57e5322
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.140977
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints383
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension383
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.01	c 	relations............. 0.06
0.08	c 	constraints........... 0.02
0.09	c Allocating memory
0.09	c 
0.09	c time limit = -1
0.09	c heuristic = dom/wdeg
0.09	c restart policy = No restart
0.09	c 
0.09	c Solving
0.09	c
0.14	s SATISFIABLE
0.14	v 20 7 2 17 17 15 10 15 5 11 1 15 1 9 4 14 2 13 5 11 14 4 12 2 1 11 9 1 15 8 20 19 7 4 11 8 12 16 1 1 3 9 1 7 19 19 1 6 1 10
0.14	d          SAT       119 BTS      0.05 s

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-230335-1168717334 -o ROOT/results/node76/solver-230335-1168717334 -C 1800 -M 900 /tmp/evaluation/230335-1168717334/mistral/bin/solver /tmp/evaluation/230335-1168717334/unknown.xml -v 1 

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: 0.51 0.93 1.42 4/73 10277
/proc/meminfo: memFree=1675832/2055888 swapFree=4095388/4096564
[pid=10276] ppid=10274 vsize=6800 CPUtime=0
/proc/10276/stat : 10276 (solver) R 10274 10276 9792 0 -1 4194304 422 0 0 0 0 0 0 0 18 0 1 0 220130783 6963200 402 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4788543 0 0 4096 0 0 0 0 17 1 0 0
/proc/10276/statm: 1700 402 363 92 0 30 0

[startup+0.104393 s]
/proc/loadavg: 0.51 0.93 1.42 4/73 10277
/proc/meminfo: memFree=1675832/2055888 swapFree=4095388/4096564
[pid=10276] ppid=10274 vsize=7976 CPUtime=0.1
/proc/10276/stat : 10276 (solver) R 10274 10276 9792 0 -1 4194304 1067 0 0 0 10 0 0 0 18 0 1 0 220130783 8167424 1036 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790735 0 0 4096 0 0 0 0 17 1 0 0
/proc/10276/statm: 1994 1036 707 92 0 337 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 7976

Child status: 0
Real time (s): 0.149423
CPU time (s): 0.148977
CPU user time (s): 0.143978
CPU system time (s): 0.004999
CPU usage (%): 99.7016
Max. virtual memory (cumulated for all children) (KiB): 7976

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.143978
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= 1077
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= 13
involuntary context switches= 27

runsolver used 0.003999 s user time and 0.002999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Sat Jan 13 19:42:17 UTC 2007


IDJOB= 230335
IDBENCH= 6408
IDSOLVER= 84
FILE ID= node76/230335-1168717334

PBS_JOBID= 3547611

Free space on /tmp= 66649 MiB

SOLVER NAME= Mistral 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-97_ext.xml
COMMAND LINE= /tmp/evaluation/230335-1168717334/mistral/bin/solver /tmp/evaluation/230335-1168717334/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-230335-1168717334 -o ROOT/results/node76/solver-230335-1168717334 -C 1800 -M 900  /tmp/evaluation/230335-1168717334/mistral/bin/solver /tmp/evaluation/230335-1168717334/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  58b6187a22c96037a9bcdd1cf57e5322

RANDOM SEED= 140935655

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:       1676184 kB
Buffers:         31312 kB
Cached:         274140 kB
SwapCached:        276 kB
Active:          76508 kB
Inactive:       248796 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1676184 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:            3436 kB
Writeback:           0 kB
Mapped:          29160 kB
Slab:            40444 kB
Committed_AS:  7476708 kB
PageTables:       1624 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= 66649 MiB



End job on node76 on Sat Jan 13 19:42:19 UTC 2007