Trace number 2091005

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.39294 0.397553

DiagnosticValue
ASSIGNMENTS250
CHECKS61212
NODES250

General information on the benchmark

Namecsp/tightness0.9/
normalized-rand-2-40-180-84-900-91_ext.xml
MD5SUM1c4d52c30b8a01d9f2e798105238c847
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.39294
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.00/0.13	c mistral version 1.545
0.29/0.37	s SATISFIABLE
0.29/0.37	v 81 20 178 49 52 110 12 94 86 144 8 160 115 37 7 93 95 88 5 75 43 179 19 127 45 140 81 136 118 54 136 163 130 76 81 23 28 146 151 113
0.29/0.37	d CHECKS 61212
0.29/0.37	d ASSIGNMENTS 250
0.29/0.37	d NODES 250 BACKTRACKS 243 FAILURES 243 RUNTIME 0.12 TOTALTIME 0.37 NODES/s 2083.33 CHECKS/s 510100

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-2091005-1247391904/watcher-2091005-1247391904 -o /tmp/evaluation-result-2091005-1247391904/solver-2091005-1247391904 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2091005-1247391904.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.01 2.01 2.00 4/74 31302
/proc/meminfo: memFree=1796056/2055920 swapFree=4192812/4192956
[pid=31302] ppid=31300 vsize=9584 CPUtime=0.19
/proc/31302/stat : 31302 (ld-linux.so.2) R 31300 31302 28825 0 -1 4194304 1582 0 0 0 19 0 0 0 19 0 1 0 26254013 9814016 1561 996147200 1448431616 1448550632 4294956208 18446744073709551615 134671741 0 0 4096 0 0 0 0 17 1 0 0
/proc/31302/statm: 2396 1561 358 29 0 1211 0

[startup+0.26461 s]
/proc/loadavg: 2.01 2.01 2.00 4/74 31302
/proc/meminfo: memFree=1796056/2055920 swapFree=4192812/4192956
[pid=31302] ppid=31300 vsize=11960 CPUtime=0.25
/proc/31302/stat : 31302 (ld-linux.so.2) R 31300 31302 28825 0 -1 4194304 2233 0 0 0 24 1 0 0 19 0 1 0 26254013 12247040 2212 996147200 1448431616 1448550632 4294956208 18446744073709551615 135277716 0 0 4096 0 0 0 0 17 1 0 0
/proc/31302/statm: 2990 2212 412 29 0 1805 0
Current children cumulated CPU time (s) 0.25
Current children cumulated vsize (KiB) 11960

[startup+0.301609 s]
/proc/loadavg: 2.01 2.01 2.00 4/74 31302
/proc/meminfo: memFree=1796056/2055920 swapFree=4192812/4192956
[pid=31302] ppid=31300 vsize=11960 CPUtime=0.29
/proc/31302/stat : 31302 (ld-linux.so.2) R 31300 31302 28825 0 -1 4194304 2233 0 0 0 28 1 0 0 19 0 1 0 26254013 12247040 2212 996147200 1448431616 1448550632 4294956208 18446744073709551615 135264259 0 0 4096 0 0 0 0 17 1 0 0
/proc/31302/statm: 2990 2212 412 29 0 1805 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 11960

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

Child status: 0
Real time (s): 0.397553
CPU time (s): 0.39294
CPU user time (s): 0.379942
CPU system time (s): 0.012998
CPU usage (%): 98.8397
Max. virtual memory (cumulated for all children) (KiB): 11960

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

runsolver used 0.002999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node50 at 2009-07-12 11:45:04
IDJOB=2091005
IDBENCH=59972
IDSOLVER=769
FILE ID=node50/2091005-1247391904
PBS_JOBID= 9507259
Free space on /tmp= 66416 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/tightness0.9/normalized-rand-2-40-180-84-900-91_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-2091005-1247391904/watcher-2091005-1247391904 -o /tmp/evaluation-result-2091005-1247391904/solver-2091005-1247391904 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2091005-1247391904.xml

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

MD5SUM BENCH= 1c4d52c30b8a01d9f2e798105238c847
RANDOM SEED=98586215

node50.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.231
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.231
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:       1796536 kB
Buffers:         33588 kB
Cached:         135596 kB
SwapCached:          0 kB
Active:         130476 kB
Inactive:        74488 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1796536 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3004 kB
Writeback:           0 kB
Mapped:          46872 kB
Slab:            39504 kB
Committed_AS:   225132 kB
PageTables:       1940 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= 66416 MiB
End job on node50 at 2009-07-12 11:45:04