Trace number 2076683

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.173973 0.184271

DiagnosticValue
ASSIGNMENTS258
CHECKS27628
NODES258

General information on the benchmark

Namecsp/rlfapGraphsMod/
normalized-graph2-f24.xml
MD5SUM032be87cbaaa5176d6390981d0a0c94f
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.173973
Satisfiable
(Un)Satisfiability was proved
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2245
Global constraints used (with number of constraints)

Solver Data 

0.08/0.18	c mistral version 1.545
0.08/0.18	s SATISFIABLE
0.08/0.18	v 254 16 128 366 366 128 338 100 100 338 100 338 254 16 16 254 394 156 114 352 16 254 72 310 114 352 72 310 352 114 254 16 296 58 72 310 366 128 310 72 16 254 268 30 324 86 254 16 268 30 30 268 380 142 254 16 30 268 58 296 268 30 142 380 44 282 100 338 86 324 142 380 114 352 16 254 268 30 114 352 254 16 282 44 324 86 324 86 156 394 282 44 352 114 254 16 114 352 72 310 30 268 380 142 30 268 282 44 100 338 268 30 30 268 324 86 156 394 142 380 268 30 30 268 72 310 268 30 142 380 16 254 16 254 380 142 352 114 114 352 296 58 366 128 338 100 72 310 156 394 254 16 310 72 142 380 16 254 16 254 254 16 380 142 254 16 72 310 114 352 114 352 44 282 16 254 268 30 142 380 142 380 30 268 310 72 282 44 142 380 324 86 86 324 310 72 100 338 352 114 394 156 352 114 338 100 352 114 86 324 366 128 142 380 156 394 100 338 72 310 72 310 268 30 254 16 380 142 296 58 114 352 128 366 128 366 268 30 44 282 296 58 86 324 44 282 142 380 86 324 16 254 282 44 380 142 114 352 380 142 394 156 142 380 142 380 86 324 44 282 58 296 324 86 338 100 268 30 338 100 282 44 268 30 142 380 58 296 16 254 380 142 380 142 114 352 142 380 380 142 282 44 44 282 30 268 338 100 380 142 380 142 142 380 30 268 380 142 72 310 156 394 156 394 58 296 296 58 86 324 394 156 366 128 338 100 268 30 380 142 268 30 352 114 268 30 72 310 142 380 380 142 72 310 156 394 58 296 100 338 324 86 30 268 310 72 268 30 156 394 114 352 156 394 86 324 268 30 156 394 58 296 338 100 352 114 58 296 100 338 156 394 156 394 86 324 16 254 142 380
0.08/0.18	d CHECKS 27628
0.08/0.18	d ASSIGNMENTS 258
0.08/0.18	d NODES 258 BACKTRACKS 79 FAILURES 79 RUNTIME 0.08 TOTALTIME 0.16 NODES/s 3225 CHECKS/s 345350

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-2076683-1247363007/watcher-2076683-1247363007 -o /tmp/evaluation-result-2076683-1247363007/solver-2076683-1247363007 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2076683-1247363007.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.22 2.26 2.17 4/84 19988
/proc/meminfo: memFree=1177608/2055920 swapFree=4192812/4192956
[pid=19988] ppid=19986 vsize=18576 CPUtime=0
/proc/19988/stat : 19988 (runsolver) R 19986 19988 18305 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 23366006 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 240153849127 0 0 4096 24578 0 0 0 17 0 0 0
/proc/19988/statm: 4644 284 249 26 0 2626 0

[startup+0.054717 s]
/proc/loadavg: 2.22 2.26 2.17 4/84 19988
/proc/meminfo: memFree=1177608/2055920 swapFree=4192812/4192956
[pid=19988] ppid=19986 vsize=5336 CPUtime=0.04
/proc/19988/stat : 19988 (ld-linux.so.2) R 19986 19988 18305 0 -1 4194304 562 0 0 0 4 0 0 0 18 0 1 0 23366006 5464064 541 996147200 1448431616 1448550632 4294956208 18446744073709551615 134615552 0 0 4096 0 0 0 0 17 1 0 0
/proc/19988/statm: 1334 541 374 29 0 149 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5336

[startup+0.101734 s]
/proc/loadavg: 2.22 2.26 2.17 4/84 19988
/proc/meminfo: memFree=1177608/2055920 swapFree=4192812/4192956
[pid=19988] ppid=19986 vsize=7172 CPUtime=0.08
/proc/19988/stat : 19988 (ld-linux.so.2) R 19986 19988 18305 0 -1 4194304 1038 0 0 0 8 0 0 0 18 0 1 0 23366006 7344128 1017 996147200 1448431616 1448550632 4294956208 18446744073709551615 134534296 0 0 4096 0 0 0 0 17 1 0 0
/proc/19988/statm: 1793 1017 398 29 0 608 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7172

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

Child status: 0
Real time (s): 0.184271
CPU time (s): 0.173973
CPU user time (s): 0.168974
CPU system time (s): 0.004999
CPU usage (%): 94.4115
Max. virtual memory (cumulated for all children) (KiB): 7172

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.168974
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= 1101
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= 25
involuntary context switches= 7

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node86 at 2009-07-12 03:43:27
IDJOB=2076683
IDBENCH=56483
IDSOLVER=769
FILE ID=node86/2076683-1247363007
PBS_JOBID= 9506972
Free space on /tmp= 66304 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/rlfapGraphsMod/normalized-graph2-f24.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2076683-1247363007/watcher-2076683-1247363007 -o /tmp/evaluation-result-2076683-1247363007/solver-2076683-1247363007 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2076683-1247363007.xml

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

MD5SUM BENCH= 032be87cbaaa5176d6390981d0a0c94f
RANDOM SEED=275061148

node86.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.265
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.265
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:       1178088 kB
Buffers:         25844 kB
Cached:          95264 kB
SwapCached:          0 kB
Active:         790064 kB
Inactive:        39152 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1178088 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1680 kB
Writeback:           0 kB
Mapped:         723760 kB
Slab:            32212 kB
Committed_AS:   870592 kB
PageTables:       3476 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= 66304 MiB
End job on node86 at 2009-07-12 03:43:27