Trace number 231209

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.110982 0.119361

General information on the benchmark

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

Solver Data (download as text)

0.11	c 
0.11	c Parsing xml file
0.11	c 	domains...............    0
0.11	c 	variables.............    0
0.11	c 	relations............. 0.07
0.11	c 	constraints........... 0.02
0.11	c Allocating memory
0.11	c 
0.11	c time limit = -1
0.11	c heuristic = dom/wdeg
0.11	c restart policy = No restart
0.11	c 
0.11	c Solving
0.11	c
0.11	s SATISFIABLE
0.11	v 3 8 12 2 2 8 2 19 2 2 2 10 17 2 6 2 5 1 4 2 5 5 3 4 13 11 5 1 2 16 2 1 12 1 6 3 1 15 9 1 2 2 2 9 7 1 12 8 10 13
0.11	d          SAT         1 BTS      0.01 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/node6/watcher-231209-1168317703 -o ROOT/results/node6/solver-231209-1168317703 -C 1800 -M 900 /tmp/evaluation/231209-1168317703/mistral/bin/solver /tmp/evaluation/231209-1168317703/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: 1.21 1.20 1.40 5/87 1915
/proc/meminfo: memFree=1311384/2055924 swapFree=4165672/4192956
[pid=1914] ppid=1912 vsize=540 CPUtime=0
/proc/1914/stat : 1914 (solver) R 1912 1914 1661 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 180165890 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2188068 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/1914/statm: 135 26 21 92 0 18 0

[startup+0.104027 s]
/proc/loadavg: 1.21 1.20 1.40 5/87 1915
/proc/meminfo: memFree=1311384/2055924 swapFree=4165672/4192956
[pid=1914] ppid=1912 vsize=7840 CPUtime=0.09
/proc/1914/stat : 1914 (solver) R 1912 1914 1661 0 -1 4194304 1045 0 0 0 9 0 0 0 18 0 1 0 180165890 8028160 1013 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790439 0 0 4096 0 0 0 0 17 1 0 0
/proc/1914/statm: 1960 1013 699 92 0 304 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7840

Child status: 0
Real time (s): 0.119361
CPU time (s): 0.110982
CPU user time (s): 0.105983
CPU system time (s): 0.004999
CPU usage (%): 92.9802
Max. virtual memory (cumulated for all children) (KiB): 7840

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.105983
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= 1066
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= 3

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Tue Jan  9 04:41:45 UTC 2007


IDJOB= 231209
IDBENCH= 6454
FILE ID= node6/231209-1168317703

PBS_JOBID= 3502596

Free space on /tmp= 66548 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-64_ext.xml
COMMAND LINE= /tmp/evaluation/231209-1168317703/mistral/bin/solver /tmp/evaluation/231209-1168317703/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-231209-1168317703 -o ROOT/results/node6/solver-231209-1168317703 -C 1800 -M 900  /tmp/evaluation/231209-1168317703/mistral/bin/solver /tmp/evaluation/231209-1168317703/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  dd4bf1a695eed3c2f35fd70bc8dab40e

RANDOM SEED= 837258352

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:      2055924 kB
MemFree:       1311864 kB
Buffers:         98932 kB
Cached:         509172 kB
SwapCached:       2944 kB
Active:         363960 kB
Inactive:       296096 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1311864 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:            3428 kB
Writeback:           0 kB
Mapped:          62368 kB
Slab:            68740 kB
Committed_AS:  5824980 kB
PageTables:       2356 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= 66548 MiB



End job on node6 on Tue Jan  9 04:41:45 UTC 2007