Trace number 2078025

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.113982 0.116637

DiagnosticValue
ASSIGNMENTS213
CHECKS406096
NODES213

General information on the benchmark

Namecsp/primes-10/
normalized-primes-10-60-3-3.xml
MD5SUM6aa59cc35c9b0e965e1e7c4e209abfeb
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.06499
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints60
Maximum constraint arity6
Maximum domain size28
Number of constraints which are defined in extension0
Number of constraints which are defined in intension60
Global constraints used (with number of constraints)

Solver Data 

0.00/0.00	c mistral version 1.545
0.09/0.11	s SATISFIABLE
0.09/0.11	v 7 17 19 13 7 13 17 5 29 3 5 19 2 29 7 12 2 17 5 17 3 2 19 29 2 2 5 7 19 13 29 5 5 23 29 19 7 17 3 5 29 7 3 29 11 19 23 2 13 2 7 17 3 2 17 7 5 2 17 3 13 13 2 19 17 13 17 29 7 19 11 13 5 13 16 19 11 11 2 2 19 23 17 23 23 11 7 20 11 29 5 2 17 23 29 5 17 17 11 29
0.09/0.11	d CHECKS 406096
0.09/0.11	d ASSIGNMENTS 213
0.09/0.11	d NODES 213 BACKTRACKS 197 FAILURES 197 RUNTIME 0.09 TOTALTIME 0.1 NODES/s 2366.67 CHECKS/s 4.51218e+06

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-2078025-1247366595/watcher-2078025-1247366595 -o /tmp/evaluation-result-2078025-1247366595/solver-2078025-1247366595 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2078025-1247366595.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.09 2.18 2.29 4/81 27518
/proc/meminfo: memFree=1825576/2055920 swapFree=4192812/4192956
[pid=27518] ppid=27516 vsize=4804 CPUtime=0
/proc/27518/stat : 27518 (ld-linux.so.2) R 27516 27518 23701 0 -1 4194304 182 0 0 0 0 0 0 0 18 0 1 0 23726954 4919296 163 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448480482 0 0 4096 0 0 0 0 17 0 0 0
/proc/27518/statm: 1201 163 138 29 0 16 0

[startup+0.0802479 s]
/proc/loadavg: 2.09 2.18 2.29 4/81 27518
/proc/meminfo: memFree=1825576/2055920 swapFree=4192812/4192956
[pid=27518] ppid=27516 vsize=5468 CPUtime=0.07
/proc/27518/stat : 27518 (ld-linux.so.2) R 27516 27518 23701 0 -1 4194304 648 0 0 0 7 0 0 0 18 0 1 0 23726954 5599232 627 996147200 1448431616 1448550632 4294956208 18446744073709551615 134839941 0 0 4096 0 0 0 0 17 0 0 0
/proc/27518/statm: 1367 627 429 29 0 182 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5468

[startup+0.10225 s]
/proc/loadavg: 2.09 2.18 2.29 4/81 27518
/proc/meminfo: memFree=1825576/2055920 swapFree=4192812/4192956
[pid=27518] ppid=27516 vsize=5468 CPUtime=0.09
/proc/27518/stat : 27518 (ld-linux.so.2) R 27516 27518 23701 0 -1 4194304 648 0 0 0 9 0 0 0 18 0 1 0 23726954 5599232 627 996147200 1448431616 1448550632 4294956208 18446744073709551615 134839745 0 0 4096 0 0 0 0 17 0 0 0
/proc/27518/statm: 1367 627 429 29 0 182 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5468

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

Child status: 0
Real time (s): 0.116637
CPU time (s): 0.113982
CPU user time (s): 0.110983
CPU system time (s): 0.002999
CPU usage (%): 97.7238
Max. virtual memory (cumulated for all children) (KiB): 5468

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

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node5 at 2009-07-12 04:43:15
IDJOB=2078025
IDBENCH=56703
IDSOLVER=769
FILE ID=node5/2078025-1247366595
PBS_JOBID= 9507038
Free space on /tmp= 66432 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/primes-10/normalized-primes-10-60-3-3.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2078025-1247366595/watcher-2078025-1247366595 -o /tmp/evaluation-result-2078025-1247366595/solver-2078025-1247366595 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2078025-1247366595.xml

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

MD5SUM BENCH= 6aa59cc35c9b0e965e1e7c4e209abfeb
RANDOM SEED=1969646794

node5.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.258
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.258
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:       1826056 kB
Buffers:          5820 kB
Cached:          72652 kB
SwapCached:          0 kB
Active:         153572 kB
Inactive:        25968 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1826056 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1260 kB
Writeback:           0 kB
Mapped:         121464 kB
Slab:            35464 kB
Committed_AS:   319348 kB
PageTables:       2004 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= 66428 MiB
End job on node5 at 2009-07-12 04:43:15