Trace number 203972

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
Tramontane 2006-12-04SAT 0.031995 0.0361339

General information on the benchmark

Namedomino/
domino-100-200.xml
MD5SUM1ab8c5d4af0025e398ba3f88141c879f
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.021996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints100
Maximum constraint arity2
Maximum domain size200
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
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 	predicates............    0
0.01	c 	constraints...........    0
0.02	c Allocating memory
0.02	c 
0.02	c time limit = -1
0.02	c heuristic = dom/wdeg
0.02	c restart policy = Geometric increment
0.02	c restart base = 69
0.02	c restart factor = 1.33
0.02	c 
0.02	c Solving
0.02	c
0.03	s SATISFIABLE
0.03	v 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199
0.03	d          SAT         0 BTS         0 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/node9/watcher-203972-1168165100 -o ROOT/results/node9/solver-203972-1168165100 -C 1800 -M 900 /tmp/evaluation/203972-1168165100/tramontane/bin/solver /tmp/evaluation/203972-1168165100/unknown.xml -res geom -f 3 -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: 2.16 2.03 2.01 4/97 17146
/proc/meminfo: memFree=1487744/2055920 swapFree=4191880/4192956
[pid=17145] ppid=17143 vsize=6792 CPUtime=0
/proc/17145/stat : 17145 (solver) R 17143 17145 16482 0 -1 4194304 422 0 0 0 0 0 0 0 18 0 1 0 164905267 6955008 401 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 8634655 0 0 4096 0 0 0 0 17 1 0 0
/proc/17145/statm: 1698 402 363 92 0 30 0

Child status: 0
Real time (s): 0.0361339
CPU time (s): 0.031995
CPU user time (s): 0.025996
CPU system time (s): 0.005999
CPU usage (%): 88.5457
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.025996
system time used= 0.005999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1004
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= 12
involuntary context switches= 62

runsolver used 0.004999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Sun Jan  7 10:18:20 UTC 2007


IDJOB= 203972
IDBENCH= 3992
FILE ID= node9/203972-1168165100

PBS_JOBID= 3478324

Free space on /tmp= 66540 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-100-200.xml
COMMAND LINE= /tmp/evaluation/203972-1168165100/tramontane/bin/solver /tmp/evaluation/203972-1168165100/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-203972-1168165100 -o ROOT/results/node9/solver-203972-1168165100 -C 1800 -M 900  /tmp/evaluation/203972-1168165100/tramontane/bin/solver /tmp/evaluation/203972-1168165100/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  1ab8c5d4af0025e398ba3f88141c879f

RANDOM SEED= 736704536

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.231
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.231
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:       1488352 kB
Buffers:         36620 kB
Cached:         207632 kB
SwapCached:        276 kB
Active:         361152 kB
Inactive:       143744 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1488352 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3276 kB
Writeback:           0 kB
Mapped:         282884 kB
Slab:            46764 kB
Committed_AS:  5168584 kB
PageTables:       2780 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= 66540 MiB



End job on node9 on Sun Jan  7 10:18:23 UTC 2007