Trace number 225355

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 9.69153 9.81721

General information on the benchmark

Nametightness/tightness0.9/
rand-2-40-180-84-900-1_ext.xml
MD5SUMfe57e07f2e5f374a3f36e0b1ff7ce6e5
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 benchmark2.94355
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints84
Maximum constraint arity2
Maximum domain size180
Number of constraints which are defined in extension84
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............    0
0.21	c 	relations............. 0.45
0.46	c 	constraints........... 0.02
0.49	c Allocating memory
0.49	c 
0.49	c time limit = -1
0.49	c heuristic = dom/wdeg
0.49	c restart policy = No restart
0.49	c 
0.49	c Solving
0.49	c
9.81	s SATISFIABLE
9.81	v 107 136 126 142 9 113 54 4 42 98 110 104 6 58 0 23 26 129 40 91 134 103 103 80 93 176 17 49 17 69 83 71 76 18 110 112 50 41 20 84
9.81	d          SAT      1589 BTS       9.2 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/node17/watcher-225355-1168272052 -o ROOT/results/node17/solver-225355-1168272052 -C 1800 -M 900 /tmp/evaluation/225355-1168272052/mistral/bin/solver /tmp/evaluation/225355-1168272052/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.92 2.22 2.61 5/95 30312
/proc/meminfo: memFree=1449256/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=540 CPUtime=0
/proc/30311/stat : 30311 (solver) D 30309 30311 29867 0 -1 4194304 41 0 0 0 0 0 0 0 18 0 1 0 175600183 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2859812 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/30311/statm: 135 26 21 92 0 18 0

[startup+0.103258 s]
/proc/loadavg: 1.92 2.22 2.61 5/95 30312
/proc/meminfo: memFree=1449256/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=8108 CPUtime=0.08
/proc/30311/stat : 30311 (solver) R 30309 30311 29867 0 -1 4194304 1096 0 0 0 8 0 0 0 18 0 1 0 175600183 8302592 1064 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2995753 0 0 4096 0 0 0 0 17 0 0 0
/proc/30311/statm: 2027 1064 692 92 0 371 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 8108

[startup+0.511299 s]
/proc/loadavg: 1.92 2.22 2.61 5/95 30312
/proc/meminfo: memFree=1449256/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=12748 CPUtime=0.49
/proc/30311/stat : 30311 (solver) R 30309 30311 29867 0 -1 4194304 2278 0 0 0 48 1 0 0 21 0 1 0 175600183 13053952 2246 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134790374 0 0 4096 0 0 0 0 17 0 0 0
/proc/30311/statm: 3187 2246 709 92 0 1531 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 12748

[startup+1.33438 s]
/proc/loadavg: 1.92 2.22 2.61 4/95 30312
/proc/meminfo: memFree=1443048/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=12748 CPUtime=1.3
/proc/30311/stat : 30311 (solver) R 30309 30311 29867 0 -1 4194304 2278 0 0 0 129 1 0 0 25 0 1 0 175600183 13053952 2246 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134637160 0 0 4096 0 0 0 0 17 0 0 0
/proc/30311/statm: 3187 2246 709 92 0 1531 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 12748

[startup+2.97455 s]
/proc/loadavg: 1.92 2.22 2.61 4/95 30312
/proc/meminfo: memFree=1442856/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=12748 CPUtime=2.93
/proc/30311/stat : 30311 (solver) R 30309 30311 29867 0 -1 4194304 2278 0 0 0 292 1 0 0 25 0 1 0 175600183 13053952 2246 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134637336 0 0 4096 0 0 0 0 17 0 0 0
/proc/30311/statm: 3187 2246 709 92 0 1531 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 12748

[startup+6.26589 s]
/proc/loadavg: 1.93 2.22 2.61 4/95 30312
/proc/meminfo: memFree=1442856/2055920 swapFree=4192812/4192956
[pid=30311] ppid=30309 vsize=12748 CPUtime=6.2
/proc/30311/stat : 30311 (solver) R 30309 30311 29867 0 -1 4194304 2278 0 0 0 619 1 0 0 25 0 1 0 175600183 13053952 2246 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134639567 0 0 4096 0 0 0 0 17 0 0 0
/proc/30311/statm: 3187 2246 709 92 0 1531 0
Current children cumulated CPU time (s) 6.2
Current children cumulated vsize (KiB) 12748

Child status: 0
Real time (s): 9.81721
CPU time (s): 9.69153
CPU user time (s): 9.67353
CPU system time (s): 0.017997
CPU usage (%): 98.7198
Max. virtual memory (cumulated for all children) (KiB): 12748

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

runsolver used 0.009998 s user time and 0.033994 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Mon Jan  8 16:00:52 UTC 2007


IDJOB= 225355
IDBENCH= 5847
FILE ID= node17/225355-1168272052

PBS_JOBID= 3483007

Free space on /tmp= 66319 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.9/rand-2-40-180-84-900-1_ext.xml
COMMAND LINE= /tmp/evaluation/225355-1168272052/mistral/bin/solver /tmp/evaluation/225355-1168272052/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-225355-1168272052 -o ROOT/results/node17/solver-225355-1168272052 -C 1800 -M 900  /tmp/evaluation/225355-1168272052/mistral/bin/solver /tmp/evaluation/225355-1168272052/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  fe57e07f2e5f374a3f36e0b1ff7ce6e5

RANDOM SEED= 405216003

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.236
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.236
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:       1449800 kB
Buffers:         68692 kB
Cached:         247236 kB
SwapCached:          0 kB
Active:         387228 kB
Inactive:       153132 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1449800 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4788 kB
Writeback:           0 kB
Mapped:         252336 kB
Slab:            50040 kB
Committed_AS:  5820548 kB
PageTables:       2672 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= 66319 MiB



End job on node17 on Mon Jan  8 16:01:04 UTC 2007