Trace number 225120

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 2.13568 2.14735

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-49_ext.xml
MD5SUM69c65ceb289035dd338a5f17db398263
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.588909
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)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	relations............. 0.22
0.22	c 	constraints........... 0.02
0.24	c Allocating memory
0.24	c 
0.24	c time limit = -1
0.24	c heuristic = dom/wdeg
0.24	c restart policy = Geometric increment
0.24	c restart base = 26
0.24	c restart factor = 1.33
0.24	c 
0.24	c Solving
0.24	c
2.14	s SATISFIABLE
2.14	v 78 19 0 0 43 2 70 34 57 23 16 44 52 67 17 79 40 41 38 60 31 20 14 37 25 57 13 20 45 17 12 5 35 37 69 36 41 47 43 54
2.14	d          SAT      1897 BTS       1.9 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/node42/watcher-225120-1168270914 -o ROOT/results/node42/solver-225120-1168270914 -C 1800 -M 900 /tmp/evaluation/225120-1168270914/tramontane/bin/solver /tmp/evaluation/225120-1168270914/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


[startup+0.104182 s]
/proc/loadavg: 2.50 2.47 2.05 5/81 25874
/proc/meminfo: memFree=1402240/2055920 swapFree=4191892/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 2.50 2.47 2.05 5/81 25874
/proc/meminfo: memFree=1402240/2055920 swapFree=4191892/4192956
[pid=25873] ppid=25871 vsize=9424 CPUtime=0.19
/proc/25873/stat : 25873 (solver) R 25871 25873 25241 0 -1 4194304 1427 0 0 0 19 0 0 0 19 0 1 0 175490792 9650176 1395 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4157853703 0 0 4096 0 0 0 0 17 1 0 0
/proc/25873/statm: 2356 1395 692 92 0 700 0

[startup+0.51222 s]
/proc/loadavg: 2.50 2.47 2.05 5/81 25874
/proc/meminfo: memFree=1402240/2055920 swapFree=4191892/4192956
[pid=25873] ppid=25871 vsize=9820 CPUtime=0.5
/proc/25873/stat : 25873 (solver) R 25871 25873 25241 0 -1 4194304 1528 0 0 0 49 1 0 0 22 0 1 0 175490792 10055680 1496 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134790655 0 0 4096 0 0 0 0 17 1 0 0
/proc/25873/statm: 2455 1496 711 92 0 799 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 9820

[startup+1.33331 s]
/proc/loadavg: 2.45 2.46 2.05 4/81 25874
/proc/meminfo: memFree=1404160/2055920 swapFree=4191892/4192956
[pid=25873] ppid=25871 vsize=9820 CPUtime=1.32
/proc/25873/stat : 25873 (solver) R 25871 25873 25241 0 -1 4194304 1528 0 0 0 131 1 0 0 25 0 1 0 175490792 10055680 1496 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134790655 0 0 4096 0 0 0 0 17 1 0 0
/proc/25873/statm: 2455 1496 711 92 0 799 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 9820

Child status: 0
Real time (s): 2.14735
CPU time (s): 2.13568
CPU user time (s): 2.12368
CPU system time (s): 0.011998
CPU usage (%): 99.4565
Max. virtual memory (cumulated for all children) (KiB): 9820

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

runsolver used 0.005999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node42 on Mon Jan  8 15:41:55 UTC 2007


IDJOB= 225120
IDBENCH= 5824
FILE ID= node42/225120-1168270914

PBS_JOBID= 3483176

Free space on /tmp= 66555 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-49_ext.xml
COMMAND LINE= /tmp/evaluation/225120-1168270914/tramontane/bin/solver /tmp/evaluation/225120-1168270914/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node42/watcher-225120-1168270914 -o ROOT/results/node42/solver-225120-1168270914 -C 1800 -M 900  /tmp/evaluation/225120-1168270914/tramontane/bin/solver /tmp/evaluation/225120-1168270914/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  69c65ceb289035dd338a5f17db398263

RANDOM SEED= 544678843

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.229
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.229
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:       1407968 kB
Buffers:         32408 kB
Cached:         112076 kB
SwapCached:        356 kB
Active:         525576 kB
Inactive:        67216 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1407968 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            3868 kB
Writeback:           0 kB
Mapped:         463796 kB
Slab:            39692 kB
Committed_AS:  4247988 kB
PageTables:       2688 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= 66555 MiB



End job on node42 on Mon Jan  8 15:41:58 UTC 2007