Trace number 2086451

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.101983 0.115237

DiagnosticValue
ASSIGNMENTS994
CHECKS152482
NODES994

General information on the benchmark

Namecsp/bibdVariousK/
normalized-bibd-9-18-8-4-3_glb.xml
MD5SUMadb817d8771232d7739b1d3c8e12e816
Bench CategoryAlldiff+Elt+WSum (alldiff,element,weightedsum)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.101983
Satisfiable
(Un)Satisfiability was proved
Number of variables810
Number of constraints711
Maximum constraint arity18
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension648
Global constraints used (with number of constraints)weightedsum(63)

Solver Data 

0.08/0.11	c mistral version 1.545
0.08/0.11	s SATISFIABLE
0.08/0.11	v 1 1 1 1 0 0 1 0 0 0 0 0 0 1 1 0 0 1 0 0 0 1 0 0 0 1 1 0 0 1 1 1 0 0 1 1 0 0 1 1 0 1 1 0 1 1 1 0 0 0 0 0 1 0 0 1 1 0 0 1 0 0 0 0 0 1 1 0 1 1 1 0 0 0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 1 1 0 1 1 1 0 0 1 1 0 1 0 0 1 0 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 1 0 0 0 1 0 0 1 0 0 0 1 1 0 0 1 1 0 0 1 1 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 1 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0
0.08/0.11	d CHECKS 152482
0.08/0.11	d ASSIGNMENTS 994
0.08/0.11	d NODES 994 BACKTRACKS 860 FAILURES 860 RUNTIME 0.05 TOTALTIME 0.09 NODES/s 19880 CHECKS/s 3.04964e+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-2086451-1247383641/watcher-2086451-1247383641 -o /tmp/evaluation-result-2086451-1247383641/solver-2086451-1247383641 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2086451-1247383641.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

[startup+0 s]
/proc/loadavg: 2.10 2.04 2.01 3/74 27493
/proc/meminfo: memFree=1741120/2055920 swapFree=4192812/4192956
[pid=27493] ppid=27491 vsize=18576 CPUtime=0
/proc/27493/stat : 27493 (runsolver) R 27491 26808 26808 0 -1 4194368 12 0 0 0 0 0 0 0 22 0 1 0 25430082 19021824 282 996147200 4194304 4302564 548682068496 18446744073709551615 254204226848 0 0 4096 24578 0 0 0 17 1 0 0
/proc/27493/statm: 4644 282 247 26 0 2626 0
Current StackSize limit: 10240 KiB


[startup+0.0761639 s]
/proc/loadavg: 2.10 2.04 2.01 3/74 27493
/proc/meminfo: memFree=1741120/2055920 swapFree=4192812/4192956
[pid=27493] ppid=27491 vsize=5728 CPUtime=0.05
/proc/27493/stat : 27493 (ld-linux.so.2) R 27491 27493 26808 0 -1 4194304 694 0 0 0 5 0 0 0 18 0 1 0 25430082 5865472 673 996147200 1448431616 1448550632 4294956208 18446744073709551615 134865479 0 0 4096 0 0 0 0 17 1 0 0
/proc/27493/statm: 1432 673 420 29 0 247 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5728

[startup+0.101161 s]
/proc/loadavg: 2.10 2.04 2.01 3/74 27493
/proc/meminfo: memFree=1741120/2055920 swapFree=4192812/4192956
[pid=27493] ppid=27491 vsize=5728 CPUtime=0.08
/proc/27493/stat : 27493 (ld-linux.so.2) R 27491 27493 26808 0 -1 4194304 694 0 0 0 8 0 0 0 18 0 1 0 25430082 5865472 673 996147200 1448431616 1448550632 4294956208 18446744073709551615 135259184 0 0 4096 0 0 0 0 17 1 0 0
/proc/27493/statm: 1432 673 420 29 0 247 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5728

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

Child status: 0
Real time (s): 0.115237
CPU time (s): 0.101983
CPU user time (s): 0.098984
CPU system time (s): 0.002999
CPU usage (%): 88.4986
Max. virtual memory (cumulated for all children) (KiB): 5728

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.098984
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= 730
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= 2

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node34 at 2009-07-12 09:27:21
IDJOB=2086451
IDBENCH=58593
IDSOLVER=769
FILE ID=node34/2086451-1247383641
PBS_JOBID= 9507190
Free space on /tmp= 66324 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/bibdVariousK/normalized-bibd-9-18-8-4-3_glb.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2086451-1247383641/watcher-2086451-1247383641 -o /tmp/evaluation-result-2086451-1247383641/solver-2086451-1247383641 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2086451-1247383641.xml

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

MD5SUM BENCH= adb817d8771232d7739b1d3c8e12e816
RANDOM SEED=144159328

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1741600 kB
Buffers:         52104 kB
Cached:         181408 kB
SwapCached:          0 kB
Active:         163740 kB
Inactive:        89604 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1741600 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1548 kB
Writeback:           0 kB
Mapped:          30520 kB
Slab:            46328 kB
Committed_AS:   258568 kB
PageTables:       1740 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= 66320 MiB
End job on node34 at 2009-07-12 09:27:21