Trace number 2090994

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 1.545SAT 0.407937 0.416011

DiagnosticValue
ASSIGNMENTS608
CHECKS100617
NODES608

General information on the benchmark

Namecsp/tightness0.9/
normalized-rand-2-40-180-84-900-61_ext.xml
MD5SUM70e6eb0da387933a6a909a0357418c76
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.407937
Satisfiable
(Un)Satisfiability was proved
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 

0.08/0.10	c mistral version 1.545
0.29/0.39	s SATISFIABLE
0.29/0.39	v 62 80 72 136 171 104 54 50 53 0 55 100 75 156 90 131 149 116 17 131 60 60 172 90 86 44 59 53 50 64 74 123 142 85 116 9 113 95 14 113
0.29/0.39	d CHECKS 100617
0.29/0.39	d ASSIGNMENTS 608
0.29/0.39	d NODES 608 BACKTRACKS 596 FAILURES 596 RUNTIME 0.15 TOTALTIME 0.38 NODES/s 4053.33 CHECKS/s 670780

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2090994-1247391866/watcher-2090994-1247391866 -o /tmp/evaluation-result-2090994-1247391866/solver-2090994-1247391866 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2090994-1247391866.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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 s]
/proc/loadavg: 2.00 1.99 1.91 3/74 24940
/proc/meminfo: memFree=1741784/2055920 swapFree=4191904/4192956
[pid=24940] ppid=24938 vsize=18576 CPUtime=0
/proc/24940/stat : 24940 (runsolver) R 24938 24940 23677 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 26249243 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 244276849959 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/24940/statm: 4644 284 249 26 0 2626 0

[startup+0.101546 s]
/proc/loadavg: 2.00 1.99 1.91 3/74 24940
/proc/meminfo: memFree=1741784/2055920 swapFree=4191904/4192956
[pid=24940] ppid=24938 vsize=7192 CPUtime=0.08
/proc/24940/stat : 24940 (ld-linux.so.2) R 24938 24940 23677 0 -1 4194304 988 0 0 0 8 0 0 0 20 0 1 0 26249243 7364608 967 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157414910 0 0 4096 0 0 0 0 17 0 0 0
/proc/24940/statm: 1798 967 358 29 0 613 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7192

[startup+0.201555 s]
/proc/loadavg: 2.00 1.99 1.91 3/74 24940
/proc/meminfo: memFree=1741784/2055920 swapFree=4191904/4192956
[pid=24940] ppid=24938 vsize=9720 CPUtime=0.18
/proc/24940/stat : 24940 (ld-linux.so.2) R 24938 24940 23677 0 -1 4194304 1615 0 0 0 18 0 0 0 21 0 1 0 26249243 9953280 1594 996147200 1448431616 1448550632 4294956208 18446744073709551615 134602815 0 0 4096 0 0 0 0 17 0 0 0
/proc/24940/statm: 2430 1594 358 29 0 1245 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 9720

[startup+0.301567 s]
/proc/loadavg: 2.00 1.99 1.91 3/74 24940
/proc/meminfo: memFree=1741784/2055920 swapFree=4191904/4192956
[pid=24940] ppid=24938 vsize=11964 CPUtime=0.29
/proc/24940/stat : 24940 (ld-linux.so.2) R 24938 24940 23677 0 -1 4194304 2230 0 0 0 28 1 0 0 22 0 1 0 26249243 12251136 2209 996147200 1448431616 1448550632 4294956208 18446744073709551615 135264290 0 0 4096 0 0 0 0 17 0 0 0
/proc/24940/statm: 2991 2209 412 29 0 1806 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 11964

Solver just ended. Dumping a history of the last processes samples

[startup+0.401576 s]
/proc/loadavg: 2.00 1.99 1.91 3/74 24940
/proc/meminfo: memFree=1741784/2055920 swapFree=4191904/4192956
[pid=24940] ppid=24938 vsize=11968 CPUtime=0.39
/proc/24940/stat : 24940 (ld-linux.so.2) R 24938 24940 23677 0 -1 4194304 2269 0 0 0 38 1 0 0 23 0 1 0 26249243 12255232 2248 996147200 1448431616 1448550632 4294956208 18446744073709551615 4159115925 0 0 4096 0 0 0 0 17 0 0 0
/proc/24940/statm: 2992 2248 450 29 0 1807 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 11968

Child status: 0
Real time (s): 0.416011
CPU time (s): 0.407937
CPU user time (s): 0.39394
CPU system time (s): 0.013997
CPU usage (%): 98.0592
Max. virtual memory (cumulated for all children) (KiB): 11968

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.39394
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2270
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= 24
involuntary context switches= 11

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node63 at 2009-07-12 11:44:27
IDJOB=2090994
IDBENCH=59965
IDSOLVER=769
FILE ID=node63/2090994-1247391866
PBS_JOBID= 9507264
Free space on /tmp= 66220 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/tightness0.9/normalized-rand-2-40-180-84-900-61_ext.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2090994-1247391866/watcher-2090994-1247391866 -o /tmp/evaluation-result-2090994-1247391866/solver-2090994-1247391866 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2090994-1247391866.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 70e6eb0da387933a6a909a0357418c76
RANDOM SEED=436581214

node63.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.232
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.232
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1742264 kB
Buffers:         54888 kB
Cached:         176800 kB
SwapCached:        260 kB
Active:         162552 kB
Inactive:        96704 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1742264 kB
SwapTotal:     4192956 kB
SwapFree:      4191904 kB
Dirty:            3036 kB
Writeback:           0 kB
Mapped:          38084 kB
Slab:            39520 kB
Committed_AS:   195884 kB
PageTables:       1920 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66220 MiB
End job on node63 at 2009-07-12 11:44:27